Messages without Name field in EMA

Hi all,
We differentiate messages received from EMA based on the name(RIC) field contained within the message.
UpdateMsg streamId="420" domain="MarketPrice Domain" updateTypeNum="0" seqNum="44766" doNotConflate name="CNH=" serviceId="600" serviceName="IDN_RDF" Payload dataType="FieldList" FieldList FieldListNum="0" DictionaryId="0" FieldEntry fid="22" name="BID" dataType="Real" value="7.1028" FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="7.1028" FieldEntry fid="25" name="ASK" dataType="Real" value="7.1032" FieldEntry fid="275" name="SEC_ACT_1" dataType="Real" value="7.1032" FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="17 SEP 2025 " FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="05:44:37:000:000:000" FieldEntry fid="831" name="CTBTR_1" dataType="Rmtes" value="2" FieldEntry fid="836" name="CTB_LOC1" dataType="Rmtes" value="2" FieldEntry fid="841" name="CTB_PAGE1" dataType="Rmtes" value="2" FieldEntry fid="3" name="DSPLY_NAME" dataType="Rmtes" value="2" FieldEntry fid="78" name="OFFCL_CODE" dataType="Rmtes" value="2" FieldEntry fid="105" name="BCKGRNDPAG" dataType="Rmtes" value="2" FieldEntry fid="826" name="DLG_CODE1" dataType="Rmtes" value="2" FieldEntry fid="1011" name="VALUE_TS2" dataType="Time" value="05:44:37:000:000:000" FieldEntry fid="1012" name="VALUE_TS3" dataType="Time" value="05:44:36:000:000:000" FieldListEnd PayloadEnd UpdateMsgEnd
However, we observe that the name field is not transmitted in many messages similar to the example below. What is the cause of this behavior? How can we effectively handle this scenario?
UpdateMsg streamId="15" domain="MarketPrice Domain" updateTypeNum="0" seqNum="63998" doNotConflate Payload dataType="FieldList" FieldList FieldListNum="0" DictionaryId="0" FieldEntry fid="22" name="BID" dataType="Real" value="3.7507" FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="3.7507" FieldEntry fid="25" name="ASK" dataType="Real" value="3.7509" FieldEntry fid="275" name="SEC_ACT_1" dataType="Real" value="3.7509" FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="16 SEP 2025 " FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="21:41:50:000:000:000" FieldEntry fid="831" name="CTBTR_1" dataType="Rmtes" value="4Y6M" FieldEntry fid="836" name="CTB_LOC1" dataType="Rmtes" value="4Y6M" FieldEntry fid="841" name="CTB_PAGE1" dataType="Rmtes" value="4Y6M" FieldEntry fid="3" name="DSPLY_NAME" dataType="Rmtes" value="4Y6M" FieldEntry fid="78" name="OFFCL_CODE" dataType="Rmtes" value="4Y6M" FieldEntry fid="105" name="BCKGRNDPAG" dataType="Rmtes" value="4Y6M" FieldEntry fid="826" name="DLG_CODE1" dataType="Rmtes" value="4Y6M" FieldEntry fid="1011" name="VALUE_TS2" dataType="Time" value="21:41:49:000:000:000" FieldEntry fid="1012" name="VALUE_TS3" dataType="Time" value="21:41:48:000:000:000" FieldListEnd PayloadEnd UpdateMsgEnd
Answers
-
Thank you for reaching out to us.
The item name in an update message is optional.
I found the MsgKeyInUpdates configuration in the Consumer.
The default value is 1 so update messages should contain item names.
However, instead of relying on the MsgKeyInUpdates configuration, you can try the following methods to solve this problem.
- Typically, each item has a unique handle, allowing the application to implement a mapping between handles and item names. The application can map a handle to an item name by parsing a refresh message
- Or, if the application doesn't use batch requests. The application can set a closure with an item name and get a closure (item name) through the OmmConsumerEvent passed in the callback methods
If you have any further question, please provide the following information.
- The version of EMA that you are using
- EMA configurations or EMA configuration file used by the application
- Is it EMA C++, Java, or C#?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 709 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.3K Eikon Data APIs
- 16 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 8 Trading API
- 3K Elektron
- 1.5K EMA
- 260 ETA
- 571 WebSocket API
- 41 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.3K Refinitiv Data Platform
- 17 CFS Bulk File/TM3
- 912 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 197 TREP Infrastructure
- 232 TRKD
- 923 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 106 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛