The second fractions were cut away inside the main stored procedures of the reports. The connectors themselves have always supported second fractions.
All report templates in these themes now support second fractions:
To roll out this fix, do this:
Important notes:
With this change, also calculated archives now support second fractions, but only when used in one of the report templates from the themes above.
As the Service Engine delivers data from cyclic archives with second fractions set to 0, all archive data from the Service Engine Connector and the SQL Connector are taken as-is without any timestamp modification. This might lead to problems when older Service Engines are in use (we investigated with zenon 7.60 - there the second fractions for cyclic archives are set to 0), where the archive module still has the "calculate milliseconds for cyclic archives" behaviour (this behaviour was removed somewhere between 7.00 and 7.60, we could not find out the exact version).
Per default, reports do not display second fractions. So, when there are multiple values for one variable within one second, there will be multiple lines in the table with the same timestamp, as the timestamps only differ in the fractions of a second which are not shown. This can be corrected by changing the format of timestamp value cells as documented here https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.
The second fractions were cut away inside the main stored procedures of the reports. The connectors themselves have always supported second fractions.
All report templates in these themes now support second fractions:
To roll out this fix, do this:
Important notes:
With this change, also calculated archives now support second fractions, but only when used in one of the report templates from the themes above.
As the Service Engine delivers data from cyclic archives with second fractions set to 0, all archive data from the Service Engine Connector and the SQL Connector are taken as-is without any timestamp modification. This might lead to problems when older Service Engines are in use (we investigated with zenon 7.60 - there the second fractions for cyclic archives are set to 0), where the archive module still has the "calculate milliseconds for cyclic archives" behaviour (this behaviour was removed somewhere between 7.00 and 7.60, we could not find out the exact version).
Per default, reports do not display second fractions. So, when there are multiple values for one variable within one second, there will be multiple lines in the table with the same timestamp, as the timestamps only differ in the fractions of a second which are not shown. This can be corrected by changing the format of timestamp value cells as documented here https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.