Inconsistency existence field data in Refinitiv DataStream
Hi guys,
We subscribe 14 RIC for get reference rate data, the method to get data is trigger scheduler to retrieve data which trigger when 5 minutes after publication time of RIC. Scheduler trigger 3 times with delay 5 minutes , 10 minutes and 15 minutes.
After develop and testing program, this program seem fine but after deploy to production, problem comes up.
SOFR Rate ( .SR1M , .SR3M , .SR6M , SR1Y ) doesn't update daily and only update at friday , after investigate raw message from source, the cause is VALUE_TS1 field disapper which is odd because when develop VALUE_TS1 exist.
Here field that used :
rate
PRIMACT_1
PRIMACT_2
PRIMACT_3
PRIMACT_4
PRIMACT_5
date
VALUE_DT => date
VALUE_TS => waktu
tenor
GV4_TEXT
So my question is:
1. is this problem common (data field disapper or changed) in all RIC ?
any possibility happen in all RIC that i subscibe ?
2. we investigate more the raw message, i found out that there are case that in rage 2 hours (17:00 - 18:00) Indonesia time , any field that i use exist but the value null, but in same day, after that range the value provided. In that case , is common happen and how to mitigate that ? (cause i am not found field that can replace field that i used)
Or do you have certain range of time to maintance your data , so i can implement retry method , if the field null or not existed ?
3. this problem brought me to more deeply understand of your data and found out interesting feature https://developers.lseg.com/en/tools-catalog/ric-search
and https://refinitiv.fixspec.com/stack/specs/elektron/world/world-refinitiv/29-0-1/2693-bonds-contributed-refinitiv-real-timemisc , so i conclude maybe because i use deprecated field, thats why its existence is uncertain.
Could you help me to explain about presence in filter ? (core , optional, if available)
4. Could you help me to mapping message from refinitiv, to get data that i use ( reference rate , publication date and time , loan term or installment duration ) to all ric ?
Note :
RIC Profile and sample data .SR1Y attached
anomaly-sr1y.txt
Best Answer
-
Thank you for reaching out to us.
Those fields are real-time fields. Their values can be changed or clear according to the market rules.
I assume that you are using WebSocket API to retrieve the data. You can contact the content support team directly via MyRefinitiv to verify the retreived content at specific times.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛