Why CF_CURR does not return currency when asking same instrument via different types of identifier?

When I ask for CF_CURR via TICKER and ISIN, I get USD for ticker but NaN for ISIN.
identifiers = ['US03076C1062', 'AMP']
data, error = ek.get_data(identifiers, fields=['CF_CURR'])
Output:
Instrument CF_CURR
0 US03076C1062 None
1 AMP USD
Is this desired behaviour that I have to first convert all identifiers to RIC (even other data can be obtained via ISIN)?
Best Answer
-
From my testing, it works with other fundamental fields, such as TR.CurrEnterpriseValueEV.
I assume that it doesn't work with CF_CURR because CF_CURR is in the Real-Time category.
Typically, we use RICs to subscribe to real-time data. If you check the raw output, you will see that it returns 'The record could not be found' for the instrument 'US03076C1062'.
{'columnHeadersCount': 1,
'data': [['US03076C1062', 28429632678.7, None],
['AMP', 28429632678.7, 'USD']],
'error': [{'code': 251658243,
'col': 2,
'message': "'The record could not be found' for the instrument 'US03076C1062'",
'row': 0}],
'headerOrientation': 'horizontal',
'headers': [[{'displayName': 'Instrument'},
{'displayName': 'Current EV', 'field': 'TR.CURRENTERPRISEVALUEEV'},
{'displayName': 'CF_CURR', 'field': 'CF_CURR'}]],
'rowHeadersCount': 1,
'totalColumnsCount': 3,
'totalRowsCount': 3}0
Answers
-
Hello @mzeman
You can use get_symbology(..) function which returns a list of instrument names converted into another instrument code e.g. ISIN is converted to RIC as an example below:
aRIC = ek.get_symbology(["US03076C1062"], from_symbol_type="ISIN", to_symbol_type="RIC")
aRIC0 -
That's not true. The answer from jirapongse.phuriphanvichai explains this problem and also provides an example that RIC is not only an acceptable identifier.
0 -
Thanks. I know this solution. I have already used it. However, it doesn't explain this problem. But jirapongse.phuriphanvichai explains it well.
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
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 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
- 275 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
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛