Dex2 Unable to collect data error
Hello,
Eikon C++ COM API, Dex2.
Randomly, we receive "Unable to collect data for all requested fields" error as a response. Sometimes it's a legit error when no data exist for all requested RICs. But sometimes it's an incorrect answer.
Today we get this error on the following request:
Instruments: CTTN.MX,CTVA.MX,CUBE.MX,CUERVO.MX,CUKN.MX,CULTIBAB.MX,CUSSN.MX,CUZ.MX,CV9N.MX,CVACN.MX,CVEN.MX,CVNA.MX,CVS.MX,CVX.MX,CWB.MX,CWEB.MX,CWEN.MX,CWI.MX,CXM.MX,CXSE.MX
Fields: TR.ISINCode,TR.SEDOLCode,TR.RICCode,TR.AssetCategoryCode
Request params:
Display params: RH:In
The response is wrong because CVS.MX has TR.ISINCode.
This looks like a bug on Eikon side which is hard to reproduce. Usually if I re-run the same request I get the data correctly.
Could you check this?
Thanks
Best Answer
-
Thank you for reaching out to us.
I am unable to replicate this issue. I can retrieve the data properly.
If the problem is hard to reproduce, please contact the Eikon Support team directly via MyRefinitiv to investigate this issue.
0
Answers
-
Hi,
Yes, it's hard to reproduce. As I mentioned in my question this happens randomly.
I opened the case with the Eikon Support team. No solution yet.
I'm copying here all the information I provided them :
---------------------
I’m adding the screenshot of our response handler for your devs. In red is the response we get for the RICs that must have the data, but the error comes instead:
Last time it happened with .MX RICs. Yesterday we ran the same query and it was fine.
(1 week ago we changed our requests to use 20 RICs in a batch request instead of 500. When we use 500 in a query, and if the issue appears, then we get hundreds of RICs without the data. This was the reason we change it to 20.)
On June 9, around 4000 RICs from the USA market returned no TR.ISINCode.
I don't know what exactly is wrong, but this looks like a bug. Maybe there is an internal timeout in Eikon logic, or maybe some cache gets corrupted... I don't know. But sometimes the data is not coming and we don't know about it, because no meaningful error is returned.
Another observation: if I go to Eikon immediately after an issue occurred, and check the data in META - ISIN is always there. However, if I check DIB, sometimes TR.ISINCode field does not exist.
One more observation: if I run the query a second time after an issue is occurred, it returns all the data correctly.
I hope this information helps.
Thanks
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 中文论坛