@jessie.lin

The blank value at the time you mentioned should be the value after closing run period. Data feed usually reset the value to blank or zero.

Considering the time 01:20 GMT, it is around 9:20 Hongkong local time and it's time before the market is open at 9:30. I think they can just skip the value.

Please find more details from the following post regarding to "+0" value and blank value. Note that we use "+0" or "0" to represent blank value in the legacy MD interface and I guess that Eikon still using the value to represent the blank data.

Hi Moragodkrit

1stly, The client couldn't skip this value.

01:00-01:30 GMT is Pre-Open Session for HKSE, so this issue not related to close run.

For RIC <2908.HK>, we published FID 22 BID as “0.01” at 01:00:12 GMT, then we published FID 22 BID as “Blank” at 01:20 GMT. From client’s end they only see the update at 01:00:12 GMT which FID 22 BID is “0.01”, which is mean, when the real market for <2908.HK> FID 22 BID is updating “0”, they still showing “0.01” .

Checked with Development team, please find the update below:

For RIC <2908.HK>, we published FID 22 in “+0” to demonstrate #blank value at 01:20:01.000 GMT 11/30/2017.

When there is NO any orders on Bid Side, our software would send “+0” to demonstrate #blank value in FID 22 because Zero is not a valid Bid Price value for Equity.

So we are suspecting Blank value can't be identified from client’s end, hence this issue occur.

Secondly, client receive Blank value through RFA API , We are help client to seek any solution about the logic how to correctly handle this value and display it ?

When checking the Post you give, it mentioned :

---------------------------------------------------- -------

In OMM RWF world there's native support for blank values by checking isBlank whereas in -Marketfeed it has to use "+0" or "0" to represent blank values and "-0" represent zero value.Blank value in OMM is the indication of an empty or null data and no value is currently present.Any previously stored or displayed value should be cleared. The contents of the data should be ignored; any display or calculation should treat the value as blank or null. Thus the application should not apply data processing when receiving blank value.

-------------------------------------------------------------

--> Could we advice client to display "+0" or "0" when they receive blank value , and "-0" when they receive 0 on Field 22 ?

Hi Moragodkrit

But how could client identify the blank value they received should be "+0" or "0" ? As they don't have additional info besides the blank value.

BRs

Jessie

@jessie.lin

You are talking about blank value which is undefined value or null. I don't understand why you need additional info besides the blank value.

As I have told you earlier, the value the application will display depending of the design of applicaiton. If they want to use string "+0" for representing the blank value they has to tell their user that "+0" value displaying on the screen is blank or null. They can also use text like "<blank>" or "<undefined>" to represent the data instead. That is the the point.

API can just provide interface for client to check the value. It does not have the rule for presenting the data on the console or screen.

Client said they didn't receive any update , which we think we send this update and with Blank value. So we are waiting for client's confirm now. please keep this case open.