data misalignment with rdp sessions

I am raising query on behalf of client that data is getting misaligned and they are using rdp platform session
client issue:
When I query the ID 4295900704 with the fields ["TR.F.StatementDate", "TR.F.PeriodEndDate", "TR.F.CashCashEquivTot", "TR.F.CashCashEquivTot.date"] and for the last 10 years (using SDATE and EDATE) it seems like TR.F.CashCashEquivTot has additional data for 2017-05-31 which I don’t get as a TR.F.PeriodEndDate/TR.F.StatementDate.
So until then the dates are equal but from then on they are one period off. I need a set of around 15 financial fields but would like to get them in a single API call.
As sometimes one or another value are missing I can’t just use TR.F.CashCashEquivTot.date for all of them. I also want to avoid to do 15 API calls for each company.
Is there any way to achieve that query without misalignment of periods/dates?
client Issue is highlighted in yellow where date and period end date is not matching with last column.
replication done from our end.
Upon reviewing the data using our get History and fundamental Reference, we are seeing correct results. For May 2017, the data appears as NA, which is expected due to unavailability.
However, on client this adjusted to columns without displaying NA and giving wrong data.NA is being filled up by adjusting the other rows
code we used:
import lseg.data as ld
from lseg.data.content import fundamental_and_referenceld.open_session()
df = fundamental_and_reference.Definition(universe = '4295900704',
fields = ["TR.F.StatementDate", "TR.F.PeriodEndDate", "TR.F.CashCashEquivTot", "TR.F.CashCashEquivTot.date"],
parameters = {'Sdate' : '-50',
'Edate' : '0',
'FRQ' : 'FI',
'Period':'FI0'
}
).get_data()
df.data.df
Code:
import lseg.data as ld
from lseg.data.content import fundamental_and_referenceld.open_session()
df = fundamental_and_reference.Definition(universe = '4295900704',
fields = ["TR.F.StatementDate", "TR.F.PeriodEndDate", "TR.F.CashCashEquivTot", "TR.F.CashCashEquivTot.date"],
parameters = {'Sdate' : '-50',
'Edate' : '0',
'FRQ' : 'FI',
'Period':'FI0'
}
).get_data()
df.data.df
I have raised the issue with product team already, but they routed to dev community team.
could you please advise on this, what is the issue here?
Answers
-
Thank you for reaching out to us.
The response is from the Datagrid endpoint on the Data Platform. You need to contact the Datagrid team to verify the response. Please refer to this case #13307519.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 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
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛