Dex2 request using ISIN
I'm testing the requests for Fundamental data using Dex2 with ISIN code as a search criteria. I saw somewhere that instead of RIC, ISIN can be used.
And it works for most of the cases.
However, I have several examples that it does not work.
ISIN: LU1536459578 . Dex2 request for TR.SEDOLCode field - return NULL
RIC for this ISIN: DLCMSGSG_t.SI . If I use RIC in the Dex2 request, it return TR.SEDOLCode: BF34791
From other side, TR.SEDOL field for ISIN has the same value as TR.SEDOLCode for RIC. But I was told not to use this field because SEDOLCode is newer and has all updates.
I have 20-30 ISINs like this. Why behavior of dex2 is different when I search for ISIN and RIC for this ISIN? I expected the search result will be linked to the same data.
Best Answer
-
You can do this using RSearch:
=RSearch("EQUITY","IssueISIN:'BMG246371030' ExchangeName:'Singapore Exchange Securities Trading Ltd' RawContextFilter:'AssetState ne \'DC\''")
Then grab the first RIC returned and use DEX2 to get the SEDOL.
0
Answers
-
You may want to verify this with Refinitiv Helpdesk, but my understanding is that the relationship between TR.SEDOL and TR.SEDOLCode is the opposite to what you were told. To the best of my knowledge TR.SEDOL has broader coverage than TR.SEDOLCode, and I've been recommending TR.SEDOL and TR.ISIN over TR.SEDOLCode and TR.ISINCode.
In any case content questions such as this one are best directed to Refinitiv Helpdesk. Btw if the Helpdesk will require replication, the issue is very easy to reproduce using Eikon Excel: =TR("LU1536459578","TR.SEDOL;TR.SEDOLCode")0 -
I talked to them and I was told twice to use TR.SEDOLCode instead of TR.SEDOL during last 2 days...I will ask them about this ISIN case.
Thanks
0 -
Another question about dex2 request using ISIN.
BMG246371030 - it returns SEDOL for RIC : 1145.HK
But there is another RIC: COUA.SI and it has the same ISIN.
Is there a way to specify an exchange name to indicate which one I want to use in request by ISIN?
0 -
I use multiple isin codes in IssueISIN. At some point it complains "Unable to read instrument list" in Excel. Is there any limitation on a length or number of ISINs in the IssueISIN parameter?
0 -
There's no such thing as "no limit". There's always a limit of some sort. Not all limits are documented though. This one isn't, so it can only be determined empirically. In my experimentation the cut off is at 59 ISINs. I.e. 60 ISINs is "too many".
0 -
I did that test too. 60 was ok, 61 - too many in my case
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
- 687 Datastream
- 1.4K DSS
- 623 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
- 255 ETA
- 557 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
- 276 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
- 689 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛