Dictionary version and missing enum values when requesting dictionary from Reuters server (hEDD)

mktdata

Hello Team,

We are requesting dictionaries from the Reuters server for the hEDD service, and we have a few questions related to dictionary versions and enum value coverage.

Currently, when we send a Dictionary Request to the Reuters server, we consistently receive the following dictionary versions:

• RDMFieldDictionary version: 4.20.68
• enumtype.def version: 25.61

However, while decoding market data using these dictionaries, we are encountering runtime exceptions related to missing enumeration values. Below is one example of the exception we see:

AN EXCEPTION HAS BEEN THROWN!Exception Type: InvalidUsageExceptionException Severity: ErrorException Classification: IncorrectAPIUsageException Status Text: Enumeration Table does NOT contain entry for enum = 43

We observe similar exceptions for multiple enum values, such as:

• 43
• 13
• 5
• 3
• 271

These exceptions indicate that the Enumeration Table does not contain the required enum entries for certain fields present in the data being decoded.

Our questions are:

1. Is it expected behavior that a Dictionary Request to the Reuters server (for hEDD or any other Service) does not always return the latest available dictionary versions?
2. Is it expected that the dictionaries provided by LSEG may not contain all enum values required for the data being published on the stream?
3. In such scenarios, what is the recommended approach?

Any guidance on whether this behavior is expected, and how best to handle missing enum values during decoding, would be greatly appreciated.

Thank you for your help.

Jirapongse

@mktdata

Thank you for reaching out to us.

You need to contact the server team via LSEG Support to update the version of data dictionary used by that server.

On the consumer side, the application may use the try/catch block to handle that exception.