question

Upvotes
Accepted
19 5 9 9

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

tick-history-rest-apirics
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@Jerome Guiot-Dorel, thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question. Thanks, AHS

Upvotes
Accepted
19 5 9 9

OK. This sounds now logical. Thank you very much for your help !

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
11.3k 25 9 14

Hi @Jerome Guiot-Dorel,

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
},


displaysourceric.png (120.3 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.