NIP data truncated by ADH cache

Piotr Gorazdowski
Piotr Gorazdowski Newcomer
in TREP APIs

Hi All,

I got a NIP service that sends this example 7byte number 1731027600945646903 to a field capable of RWF length of 8 which I assume means 8 bytes as well so it should fit within the range just fine.
LASTUPDATE "LASTUPDATE" 20101 NULL INTEGER 15 UINT64 8

However ADH cache truncates the data stating it is to large.
Any idea why this is happening?

Thanks

Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @Piotr Gorazdowski

    Thank you for reaching out to us.

    I tested it with ADS POP 3.8.0.L1. It works properly.

    The NIProvider published the following refresh.

    image.png

    Then, the consumer got the following refresh from ADS POP.

    image.png

    You need to make sure that ADH and ADS loaded the modified dictionary and all components (ADH, ADS, NIProvider, and Consumer) used the same dictionary.

    You can contact the ADH support team directly via MyAccount to verify the ADH configurations. 

Categories