Ripple To functionality / JSFC 356E3

ashwini_jakhar
ashwini_jakhar
in TREP APIs

cusersf359528desktoprealtimerealtimeupdatetest.zipcusersf359528desktopemail.pdf

Reuters team,

Please see attached email and sample program to reproduce this issue

We would like to better understand how Reuters makes the decision to “RippleTo” the next field. Some RICS ( 2 Year Swap ) have just one entry for BID and other RIC ( 5 year Swap ) has multiple entries and it ripples thru to the next field.

How can we turn this off ?

We attempted explicit programmatic change on our end to set it to false but it seems to make no difference. This setting seems to be controlled by Reuters library.

Tagged:

Best Answer

  • Gurpreet
    Gurpreet
    Answer ✓

    @ashwini_jakhar The ripple fields are set at headend and application can not turn it off. An API subscriber application can selectively ignore any FID, including ripple fields.

    Can your application be modified to ignore these fields?

Answers

  • Jonathan Haruni - Refinitiv
    Jonathan Haruni - Refinitiv

    Can you please explain why you want to turn off ripple fields? You are probably trying to achieve something that should be done some other way. When ripple fields are defined in a record, their purpose is to hold previous values of the primary field. That is what they are for. There is no way to "turn them off" through the API and moreover there would be no point. If you turn them off they will just be empty, you may as well just ignore them to begin with. Can you please explain what you are attempting to do with this? In your attached code sample you appear to be trying to "freeze" a ripple field based on some condition. That won't work. Can you describe the intent of that in business terms?

    Also, I'd like to add that if you are actively developing or maintaining your application you should consider migrating to a newer Thomson Reuters API. JSFC is over 20 years old. If you have the covers off and are writing code, now is the time to leap frog 3 major generations of API evolution and use a modern TR API that will be a lot easier to maintain. If you would consider that please inform your Technical Account Manager who will arrange a conversation with TR's Developer Advocacy team to help you.

Categories