For some types of trend data, a dot is added after the value when trend data is requested via an SLNet call, regardless of decimals or culture. For example, "60." gets returned for a trend point where a parameter had value "60". These dots are not shown in the resulting trend graph and are likely ignored during parsing.
What is the function of these dots, and would it be a problem if they were omitted in the responses of trend data requests?
Alexander Verriest [SLC] [DevOps Advocate] Selected answer as best 19th May 2021
The dot happens when a double-value happens to be a whole number (example, 8.00), somewhere down the line a string conversion causes these numbers to parsed to 8., omitting the zeros.
Removing this should not pose issues for trend data responses.
Alexander Verriest [SLC] [DevOps Advocate] Selected answer as best 19th May 2021