Unexpected field "Alias Underlying RIC" in CSV files

Hello,
We have recently met a new column in our TRTH weekly extractions which is named 'Alias Underlying RIC'. We apparently did not change anything to our process.
We did not receive any product change notifications about it.
Is it something which is going to last ?
How can we be aware of these format modifications ?
Best regards
Jerome Guiot-Dorel
Best Answer
-
OK. This sounds now logical. Thank you very much for your help !
0
Answers
-
I have found some information about the issue. The field is generated by Display Source RIC feature which is broken previously. The feature has been fixed last week. It was a mistake that there was no PCN. For these kind of changes next time, PCNs will be issued with 2-3 weeks advance notice allowing clients adequate time to adjust their applications.
Below is the response from TRTH support team.
The feature of Display Source RIC was available in TRTH v1, but was not working as per design in TRTH v2. This feature is extensively utilized by many of TRTH clients to identify the source RIC information, especially for Futures Alias instruments (e.g. CLc1) the feature allows users to identify the underlying source RIC or expiration right through history.
The design of this ‘Display source RIC’ in TRTH v2 was fixed on our primary data center this weekend, will be replicated in our secondary data center this Wednesday. When the feature is checked an additional column ‘Alias Underlying RIC’ is included in the Tick History extraction results.
If you don’t find value in the feature or if your applications are hard-wired with a fixed list of columns you are requested to uncheck the feature as demonstrated below.
If you are using GUI, please disable “Display source RIC” as highlighted in the screenshot below:If you are using REST API, please make the below changes to your API code to disable the “Display source RIC” functionality.
"Condition": {
"ApplyCorrectionsAndCancellations": false,
"QueryStartDate": "2004-01-05T00:00:00",
"QueryEndDate": "2004-02-04T00:00:00",
"ReportDateRangeType": "Range",
"MessageTimeStampIn": "GmtUtc",
"DisplaySourceRIC": false
},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 中文论坛