Hi team!
We have developed a software that publishes market data to a TREP system: first an initial Refresh Message, and then Update Messages which contain only the fields that have changed (bid/ask/mid prices and timestamp).
However, on the target system, the item seems to contain dozens of fields that we have set neither in the Refresh nor in the Updates. These fields have invalid values like special characters.
As the invalid fields mess up the client's UI display, we bypass the issue by sending only Refresh Messages - but this is not a long-term solution.
When we connect a simple test consumer (taken from the RTSDK) with the target TREP system (i.e. we consume the market data we are publishing ourselves), the first RefreshMsg we receive contains the additional invalid fields; all further Refreshes contain only the fields we explicitly set in the message (→ see attached log file).
My question is: where do these unwanted fields come from? Can there be an issue on our side - e.g. something with our EmaConfig or the dictionary?
Thank you in advance!
Helmut