@neil.gallagher, sorry for the late reply.

If a RIC has changed will a request with the old RIC bring back data with the new RIC

No. Requests must be made with the current name, not an old name.

Is there a better way to do this?

For your use case (daily request for a set of RICs), the best approach is to use the RIC maintenance reports. They contain: Deletions, Renames, Currency Conversions, Delists, Relists, File Code Updates and Stock Split Adjustment Factors.

There are 2 things you need to do:

1. Set-up: enable RIC maintenance reports in the user preferences in the GUI:

2. Daily: process the RIC maintenance reports

2.a. Retrieve the report file. Note that if there are no changes, the file is empty.

2.b. Process the file to extract the information you require. For instance, you can extract RIC renames, and modify your data requests accordingly to use the latest name.

Further references

The report is in CSV format, a detailed description can be found here.

.Net SDK tutorial 3 introduces this topic, see in particular here and (much further down) under heading "Retrieving the extracted data".. .Net SDK tutorial 4 describes the preference setting and file retrieval for a scheduled extraction.

The REST API Tutorial 10 also covers this (using Postman) for a scheduled request.

@neil.gallagher, for a data related query like this one, the best and speediest way to receive an answer is to to contact your assigned product specialist directly. Alternatively you can open a content-related enquiry via My Account or call the Thomson Reuters Help Desk directly.

@Christiaan Meihsl - Does this maintenance report also cover off CUSIP changes as well? My customer is having a difficult time keeping up with them and their system ends up creating a new one and keeps the old one thus having 2 records. Here is their inquiry verbatim:

We get retired/old CUSIPs from custodians in some cases and will use it for new security creation. In IDC it would determine that we were referencing a security by a retired CUSIP and give us the data we requested and fix the CUSIP for us in that dataset. Datascope continues to keep shells of securities with a RIC for some time after a CUSIP change and we end up creating a security based on the shell of the retired CUSIP. What is the correct logic for determining if the security data we requested is from a retired CUSIP so that we can perform some other query to find the current/valid CUSIP?

@mark.tabora,

Q: Does this maintenance report also cover off CUSIP changes as well?

A: As far as I know, it does not. Even though DSS delivers cross reference data, it is a RIC centric product, and the maintenance report contents reflect that.

For the correct logic to handle retired CUSIPs, please direct this to the help desk, as that query is not related to software development, and our moderators do not have the required deep expertise in all the content sets available through our products to answer your question.