Ripple To functionality / JSFC 356E3

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.
Best 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?
0
Answers
-
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.
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
- 249 ETA
- 554 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 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 中文论坛