We're consuming data using the Real Time SDK (https://github.com/Refinitiv/Real-Time-SDK/tree/master

dwarika.natham

We're consuming data using the Real Time SDK ().

When opening the item JPYNOK=X, we get a reasonable call to OnRefreshMsg() with a conversion rate and a scaling of 100.

However, when we receive calls to OnUpdateMsg() for this item, the scaling is set to 1.

We believe this is a bug. Are you able to confirm and possibly fix this?

https://github.com/Refinitiv/Real-Time-SDK/tree/master

Jirapongse

@dwarika.natham

Thank you for reaching out to us.

Can you share the retrieved data? I checked the data on Tick History and saw this update.

JPYNOK=X,Market Price,2024-11-30T17:56:37.970626173Z,+0,Raw,REFRESH,,,,,363,99,0,,226

,,,,FID,1,,PROD_PERM,363,

,,,,FID,2,,RDNDISPLAY,153,

,,,,FID,3,,DSPLY_NAME,Refinitiv,

,,,,FID,5,,TIMACT,21:59:00.000000000,

,,,,FID,11,,NETCHNG_1,0.0665,

,,,,FID,12,,HIGH_1,,

,,,,FID,13,,LOW_1,,

,,,,FID,15,,CURRENCY,578,NOK

,,,,FID,17,,ACTIV_DATE,2024-11-29,

,,,,FID,19,,OPEN_PRC,,

,,,,FID,21,,HST_CLOSE,7.3562,
,,,,FID,22,,BID,7.3562,

,,,,FID,23,,BID_1,7.3562,

,,,,FID,24,,BID_2,7.3562,
,,,,FID,25,,ASK,7.3856,

,,,,FID,26,,ASK_1,7.3856,

,,,,FID,27,,ASK_2,7.3856,
….
JPYNOK=X,Market Price,2024-11-30T18:00:00.399938655Z,+0,Raw,UPDATE,QUOTE,,,,363,,80,,48
,,,,FID,22,,BID,7.3562,

,,,,FID,393,,PRIMACT_1,7.3562,
,,,,FID,25,,ASK,7.3856,

,,,,FID,275,,SEC_ACT_1,7.3856,

,,,,FID,875,,VALUE_DT1,2024-11-29,

The API just retrieves data from a data feed and then dispatch it to an application. It will not modify the data.

You may need to check your application logic or contact the content team via MyAccount to verify the data.

dwarika.natham

Hello jirapongse,

Please find below the update from client. I will also add the extraction provided.

Please find the attached the log for JPYNOK for 11-12-2024T22:15:24:487Z , the scaling is missing here , and in the other case of GBPNOK we received scaling as 1. It would be nice if you can help us understand the inconsistent nature of the Scaling field.

JPYNOK=X.txt

GBPNOK=X.txt

Jirapongse

@dwarika.natham

Typically, the data is deliveried in refresh and update messages.

After sending a request message to a server, the server will respond with a refresh message which contains all fields available for a subscrived RIC. In short, a refresh message will contain all fields including the SCALING field.

When there are market activites or price changes, the server will send an update message which contains only updated fields. This mean that the values of other fields remain the same.

The update of JPYNOK=X didn't have the SCALING field which means the value of the SCALING field didn't change.

This is a refresh message of JPYNOK=X which contiains the SCALING field.

For a question regarding why the update of GBPNOK=X contains the SCALING field, please contact the content support team directly to verify the content.

dwarika.natham

Hello Thanks for the update. Do you think we have something for the below client is asking:

But that does not explain the scenario where we have received Scaling= 1. How should that be interpreted ?

dwarika.natham

wasin.w

Hello @dwarika.natham

Please be informed that the API just receives incoming data from the Real-Time platform "as is". When an application/API receives an update message with SCALING field value as 1, it means the Real-Time feed sends that data to the consumer.

To verify this data behavior, I strongly suggest you contact the Real-Time support team directly. You can contact the team via https://myaccount.lseg.com/en/productsupport website.