Publications on TREP via Eikon Excel

Is anyone aware of what would cause a NAK error when publishing to BID field a value like this 1.123456789 and yet it works fine with 1.12345678 when publishing to an internal source defined on ADH?

I don’t see any restrictions as far as the BID Field is defined in the data dictionaries on TREP.

Find more posts tagged with

trep

rfa

elektron

ADH

refinitiv-realtime

Accepted answers

LtDoolittle6

I did some test recently around this area and it appeared to be that Eikon Excel has limitations when it comes to Posting a value with more than 8 decimal places. Wrote some code in RFA Java OMM and was able to Post up to 14 decimal places without any problems and I could consume that record just fine in Eikon and standard RFA consumer application without any issues.

Populate FID 25 : ASK with Real 0.00000000000001 to 14 decimal places (EXPONENT_NEG14)
value = 0.00000000000001;
longValue = Rounding.roundDouble2Long(value, OMMNumeric.EXPONENT_NEG14);
_postOMMEncoder.encodeFieldEntryInit((short)25, OMMTypes.REAL);
_postOMMEncoder.encodeReal(longValue, OMMNumeric.EXPONENT_NEG14);

All comments

LtDoolittle6

EXPLORE OUR SITES