Workspace/Eikon Python API: CF_ fields available for one login but not for another

Hello,
When we run the following get_data query in Python using one login, we receive data but with another login no data comes up:
rd.get_data('0005.HK', fields=['CF_CLOSE', 'CF_CURR', 'CF_BID', 'CF_ASK'])
Support team has no idea why this is the case and suggested to ask here.
Anyone has any idea why?
Thanks in advance!
Best Answer
-
You may use other TR fileds instead, such as TR.TPEstCurrency.
rd.get_data('/0005.HK', fields=['CF_CLOSE', 'CF_CURR', 'CF_BID', 'CF_ASK',"TR.TPEstCurrency"])
However, you need to contact the helpdesk team direclty via MyRefinitiv to verify if this field can be used.
0
Answers
-
Thank you for reaching out to us.
To verify what the problem is, you need to enable the debug log in the library by using the following code.
import refinitiv.data as rd
rd.get_config()["logs.level"] = "debug"
rd.get_config()["logs.transports.file.enabled"] = True
rd.get_config()["logs.transports.file.name"] = "refinitiv-data-lib.log"
rd.open_session()With the code, the refinitiv-data-lib.log will be created. Please share this file when the problem occurred.
Typically, it could be permission issues, if you use different accounts.
0 -
Hello,
Here is the file
20240419-1236-52980-refinitiv-data-lib.zip
What permission would need to be activated?
Thanks.
0 -
I checked the log file and found that the accout doesn't have permission to access real-time data of 0005.HK.
[2024-04-19T12:36:57.405107+08:00] - [sessions.desktop.workspace.0] - [DEBUG] - [56784 - ThreadOMMSTREAMING_PRICING_0.0] - [stream_connection] - [_on_message] - [OMMSTREAMING_PRICING_0.0] on_ws_message [{"ID": 5, "Type": "Status", "Key": {"Service": "IDN_FD3", "Name": "0005.HK"}, "State": {"Stream": "Closed", "Data": "Suspect", "Code": "NotEntitled", "Text": "Access Denied: User req to PE(4945)"}}]
Please contact your LSEG account team or sales team directly to verify the permission. Otherwise, you can use delayed RICs (/0005.HK) instead.
rd.get_data('/0005.HK', fields=['CF_CLOSE', 'CF_CURR', 'CF_BID', 'CF_ASK'])
0 -
Thanks a lot @Jirapongse !
Would you know also for the CF_CURR field using the refinitiv.data API, how to get the actual currency code instead of the number value? Ex: HKD for 344.
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.4K 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
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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 中文论坛