Why some message miss subscribed fields?

Best Answer
-
Hello @joelxzhang
Views feature that you use allows the client application to request specific fields. After the feed/exchange sends the fields to the server, the server will filter out the fields which you do not request so only requested fields sent to you. Hence, the feature does not guarantee that every message contains all fields you specific. This depends on the feed which generates/sends the fields of each message to the server. In your case the feed did not generate QUOTE_DATE and QUOTIM_MS in every message that why's you received only ASK and BID which you specific in the request.
This is data question that the feed does not send "QUOTE_DATE", "QUOTIM_MS" with ASK and BID in every message. I would suggest you reach out to the Refinitiv Helpdesk as they have feed/data specialists who can help you on this.
0
Answers
-
But I need to know when the data generated by refinitiv, and someone told me that these two fields express the time point the data create. Or you can suggest me another field to the usage?
0 -
Hello @joelxzhang
Sorry. I am not data expert and do not know the answer. Please contact Refinitiv Helpdesk who can answer data questions.
This forum is dedicated to questions and discussions on Refinitiv APIs, rather then data questions, the majority of the members of the community are developers, the moderators of the forum are API experts.
0 -
Hello @joelxzhang
If you are using a streaming request, it is an expected behavior as mention by my colleague (Pimchaya). The only to way to let TREP/Elektron always returns all requested fields is to use a snapshot request.
A snapshot request is a request for one response without the intent to receive updates. The data stream is considered closed after the data is received by the consumer because the request has been fulfilled. You can send a snapshot request via the Elektron WebSocket API with "Streaming" : false attribute in the request message.
{
"ID": 2,
"Key": {
"Name": "EUR="
},
"View": [
"BID",
"ASK",
"QUOTE_DATE",
"QUOTIM_MS"
],
"Streaming": false
}0 -
Hi @joelxzhang
The most likely reason why some updates do not contain QUOTE related fields is because that update is for a Trade type event - rather than a Quote type event. For Trade type events the Trade related fields e.g. TRADE_DATE would be sent.
However, as mentioned by my colleague it is best to check with the Content Helpdesk for your particular instruments/RICs.
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛