Pricehistory for Date Range get Requested Date in Result

I am doing the following Request in code book, that i need to replicate in C#
import refinitiv.data as rd
rd.open_session()
df = rd.get_data(
universe = ['NCSM.O','ZYNE.O'],
fields = [
'TR.PriceClose',
'TR.Volume',
'TR.PriceCloseDate'
],
parameters={
'SDate': '2024-09-11',
'EDate': '2024-09-01'
}
)
display(df)
And i get this result
result
0 NCSM.O20.415902 2024-09-11
1 NCSM.O20.884412988 2024-09-10
2 NCSM.O21.555194 2024-09-09
3 NCSM.O20.864047 2024-09-06
4 NCSM.O21.1711898 2024-09-05
5 NCSM.O20.964102 2024-09-04
6 NCSM.O20.7418982 2024-09-03
7 ZYNE.O1.302023-10-10
8 ZYNE.O1.302023-10-10
9 ZYNE.O1.302023-10-10
10 ZYNE.O1.302023-10-10
11 ZYNE.O1.302023-10-10
12 ZYNE.O1.302023-10-10
13 ZYNE.O1.302023-10-10
As you see for ZYNE i get the Last Priced Date,
Is there a way i can add to my series, the date that the response is for?
for example
7 ZYNE.O1.302023-10-10.2024-09-11
8 ZYNE.O1.302023-10-10.2024-09-10
9 ZYNE.O1.302023-10-10.2024-09-09
10 ZYNE.O1.302023-10-10.2024-09-06
11 ZYNE.O1.302023-10-10.2024-09-05
12 ZYNE.O1.302023-10-10.2024-09-04
13 ZYNE.O1.302023-10-10.2024-09-03
Here is the code i use to run in C#
Frame<int, string> frame = privateEikon.GetData(
securities,
fields,
new Dictionary<string, string> { { "SDate", startDate }, { "EDate", endDate }, { "Frq", "D" } }
);
Best Answer
-
Thank you for reaching out to us.
I found that the ZYNE.O has been delisted in 2023 and the lastest price was on 10-10-2023. You can contact the content support team directly via MyAccount to verify this.
For C#, please use the Refinitiv Data Library for .Net. The sample code is available on GitHub. The code looks like this:
response = FundamentalAndReference.Definition().Universe("NCSM.O","ZYNE.O")
.Fields("TR.PriceClose.Date","TR.PriceClose","TR.Volume")
.Parameters(new Newtonsoft.Json.Linq.JObject()
{
["SDATE"] = "2024-09-01",
["EDATE"] = "2024-09-11",
["FRQ"] = "D"
}).GetData();The output is:
If the product returns the close price of ZYNE.O on 2024-09-11, it will confuse many users because this RIC is not a valid RIC anymore.
0
Answers
-
to clarify the reason i need to do this, is becuase i request a group of fields, incluiding volumen a vwap, and this is important to know for what date i requested it.
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
- 622 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
- 254 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
- 671 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
- 229 TRKD
- 918 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
- 48 中文论坛