Variable (falsely) includes Project + Archive names, therefore exceeding the lenght prematureley

• Related Articles

• It should be possible to display long variable names in the archives dialog when the extended trend and report viewer screens data origin is the archive.

  Summary Long variable names do not fit in the historian tree of the extended trend and report viewer screens archives dialog, so that when the ending part is in view by scrolling, the beginning part is no longer visible. Description Long variable ...

• The variable identification in the archive revision filter dialog is not translated by the language switch function.

  Summary If you use a language switch function the keyword used in the variable identification in the archive revision filter dialog is not considered and therefore not translated. DescriptionIf you use a language switch function the keyword used in ...

• XML import does not accept colon in tag names

  Description The import of a zenon Logic project from an XML file fails. The cause is colons in variable names. These lead to the import being aborted. This behavior has been modified. Colons in variable names are processed correctly again during ...

• ArchiveVariables.Item(0) contains the trigger variable of an archive instead of the first archive variable

  Summary In version 6.51 SP0 Build 8 and before, the definition for ArchiveVariables.Item(0) was that this element should contain the first variable of the archive. From there on, it contains the trigger variable. This also applies to version 7.00 ...

• OPCUA client driver after the build 55804 generates with the variable import wrong variable names

  Summary OPCUA Client driver generates wrong variable names at import (after build 55804) Description OPCUA Client driver generates wrong variable names at import (after build 55804) Information For the version 7.60 and 8.00 exists the posibility to ...