How to get Index Name and Constituents in the same Extraction

Hi, if I set up an instrument list with several Index Chain RICs, they become expanded in the extraction to their constituents. Is there a possibility to see in the extraction, from which index each RIC was expanded i.e. a reference to the original Chain RIC per entry? Is there a special report Template/Field to achieve this? The desired format would be:
<parent index (or parent index chain RIC)>;<RIC>;<ISIN>
Best Answer
-
Hello @f.heuschen,
Depending on what request type you are running, Identifier included with the result is the original request Identifier, so may carry the info you are looking for?
For example:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.EndOfDayPricingExtractionRequest",
"ContentFieldNames": [
"Ask Price",
"CUSIP",
"Exchange Code",
"Exchange Description",
"RIC",
"Ticker"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "438516AC0", "IdentifierType": "Cusip" },
{ "Identifier": "IBM.N", "IdentifierType": "Ric" },
{ "Identifier": "0#US30YT=TWEB", "IdentifierType": "ChainRIC" }
]
},
"Condition": null
}
}results in
{
"IdentifierType": "ChainRIC",
"Identifier": "0#US30YT=TWEB",
"Ask Price": 152.60938,
"CUSIP": "912810QK7",
"Exchange Code": "TWB",
"Exchange Description": "TRADEWEB",
"RIC": "912810QK7=TWEB",
"Ticker": "UST"
},
{
"IdentifierType": "ChainRIC",
"Identifier": "0#US30YT=TWEB",
"Ask Price": 160,
"CUSIP": "912810QL5",
"Exchange Code": "TWB",
"Exchange Description": "TRADEWEB",
"RIC": "912810QL5=TWEB",
"Ticker": "UST"
},
{
"IdentifierType": "ChainRIC",
"Identifier": "0#US30YT=TWEB",
"Ask Price": 169.98438,
"CUSIP": "912810QN1",
"Exchange Code": "TWB",
"Exchange Description": "TRADEWEB",
"RIC": "912810QN1=TWEB",
"Ticker": "UST"
},Does this help?
0
Answers
-
Thanks for the answer.. is this only the case on using the REST Service? I tried the same with the DSS Frontend ( EOD Request with RIC & ISIN as fields) and here the parent chain RIC was not included in the created file...
0 -
Hello @f.heuschen,
From my looking via DSS GUI request this does not seem to be the case. However, to get a definitive answer, if there is an option to obtain this info with results via DSS GUI, it is best to involve a Refinitiv DSS specialist via Refinitiv Helpdesk Online -> DSS.
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
- 684 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
- 251 ETA
- 555 WebSocket API
- 37 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
- 643 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
- 916 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 中文论坛