Retrieve historical Ultimate Parent given a LEI

I am creating a historical database to track track the relationships between fund managers and the ultimate parent of a fund. To do this, I am using the LSEG Python API.
I have been testing this procedure using the rd.get_data() function. This allows me to retrieve the name and PermID of the ultimate parent for a list of LEIs. I have tested this with a large sample of funds and it works very well.
I am now trying to generalise this to a dynamic setting with the help of the rd.get_history() function, but this does not seem to work, as the retrieved fields seem 'static'. Is there any way to overcome this issue?
Please see a simple code preview of the issue below:
# Works
import refinitiv.data as rd
rd.open_session()
df = rd.get_data( universe = ['95980020140005636071@LEI' ],
fields = ['TR.UltimateParent', TR.UltimateParentId'] )
# Does not work
df = rd.get_data( universe = ['95980020140005636071@LEI' ],
fields = ['TR.UltimateParent', TR.UltimateParentId'] )
interval="3M", start="2024-01-01", end="2024-12-31")
I get the following error:
"RDError: Error code -1 | Output parameter 'date' is unrecognized. This could possibly happen because of mismatch between top level function expression and its usage in output. Make sure that you used exactly 1:1 identical expressions. Requested universes: ['5000069571']. Requested fields: ['TR.ULTIMATEPARENT', 'TR.ULTIMATEPARENTID']"
Answers
-
Thank you for reaching out to us.
I checked those fields on Data Item Browser and found that they don't support historical data.
Please contact the helpdesk team directly via the LSEG Support to confirm this.
0 -
I have checked with the content team, who have confirmed that the following item does not support historical data.
Are there any known alternatives to resolve this issue?0 -
This forum is dedicated to software developers using LSEG APIs. The moderators on this forum do not have deep expertise in every bit of content available through LSEG products, which is required to answer content questions such as this one.
The best resource for content questions is the Helpdesk support team, which can be reached by submitting queries through the LSEG Support. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you.
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 中文论坛