"Invalid value (fixed area)"

Working through this tutorial: EMA Consumer - Posting data to TR Contribution Channel (C/C++) and getting an error when posting data. The spec I'm working from specifies two fids: BID (Fid 393) and Date (Fid 875) and as a test I want to send two hard-coded values, 4.26 and 10/31/2019. Here's how the payload is created:
.payload(FieldList()
.addReal(393, 426, OmmReal::ExponentNeg2Enum)
.addDate(875, 2019, 10, 31)
.complete()))
This results in:
AckMsg
streamId="5"
domain="MarketPrice Domain"
ackId="1"
nackCode="DeniedBySource"
text="Invalid value (fixed area)"
AckMsgEnd
What does "Invalid value (fixed area)" mean? Is there a problem with one of the fields? Are there fields missing? Any ideas?
Best Answer
-
I got the same error when contributing to the value of FID 875 (VALUE_DT1).
.payload(FieldList()
.addDate(875, 2019, 11, 8)
.complete()))AppClient::onAckMsg :: AckMsg
streamId="5"
domain="MarketPrice Domain"
ackId="14"
nackCode="DeniedBySource"
text="Invalid value (fixed area)"
AckMsgEndIt works fine if I contribute only FID 393 (PRIMACT_1).
.payload( FieldList()
.addReal(393, 426, OmmReal::ExponentNeg2Enum)
.complete() ))I have also subscribed to that contributed item and found that the update message contains both FID 393 and 875.
UpdateMsg
streamId="5"
domain="MarketPrice Domain"
updateTypeNum="0"
DoNotConflate
seqNum="59566"
name="TRCCTEST01"
serviceId="2115"
serviceName="API_ELEKTRON_EPD_RSSL"
Payload dataType="FieldList"
FieldList
FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="07 NOV 2019"
FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="03:42:58:000:000:000"
FieldEntry fid="270" name="ACT_TP_1" dataType="Enum" value="0"
FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="4.26"
FieldListEnd
PayloadEnd
UpdateMsgEndI assume that the value of FID 875 is generated by TRCC and the application is not allowed to contribute to this field.
However, you need to directly contact the TRCC support team for confirmation. Please visit my.refinitiv.com and select the "Thomson Reuters Contributions Channel" product.
0
Answers
-
Yes, the support team came up with the same suggestion and it worked. Thank you for your response.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛