When having a project converted from 7.11 to 7.20 and evacuating archives to SQL database, it is not possible to change values (enter manual values, MAN_VAL) which were created in 7.11 with the archive Revision or report generator, the saving of the value change has no effect.
Summary
When changing a value manually with archive Revision which was created after the conversion to 7.20, the value is changed in the archive, in the table of the SQL database and can also be seen in the trend. When doing the same procedure with a value which was created in 7.11 (before conversion to 7.20), the value change is not recognized (Value is NOT changed in the SQL table)
Description
When changing a value manually with archive Revision which was created after the conversion to 7.20, the value is changed in the archive, in the table of the SQL database and can also be seen in the trend. When doing the same procedure with a value which was created in 7.11 (before conversion to 7.20), the value change is not recognized (Value is NOT changed in the SQL table)
Solution
enabled that NULL values in GUID colums are supported again
Information
With this KB entry the FAQ entry 295233 is solved
Issue Number: 34073
Fixed on Date: 24.3.2015
Versions: 7.20 0 BUILD 18778
Related Articles
FAQ: After updating to zenon 7.20 I dont see newly SQL evacuated historian data anymore in the trend (ETM), Report Generator, Report Viewer and Archive Revision, only the former evacuated values are displayed.
Summary Solution There is an available update, see Article ID195426 / ID165155. We highly recommend to update to the linked build ID195426 If you do not update, there is a Workaround Change the GUID column of the table from CHAR to VARCHAR. With ...
FAQ: What is the difference between the zenon Report Generator and the zenon Report Viewer?
The zenon Report Generator and Report Viewer combine to make up the module "zenon Reporting". The Report Generator, Report Viewer, or both styles can be used in your zenon HMI/SCADA projects. Each style has its own advantages and compliments ...
Archive configuration for best SQL evacuation performance
The time required to evacuate data to a database increases linearly with the number of insert SQL statements. In earlier zenon versions, recorded values were evacuated to the target database sequentially using single-insert statements. From zenon 11 ...
Checklist: Workspace/Project cannot be created, loaded or backed up
Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...
After updating to zenon 7.20 I dont see newly SQL evacuated historian data anymore in the trend (ETM), Report Generator, Report Viewer and Archive Revision, only the former evacuated values are displayed.
Summary When having a 7.11 project and evacuating archives to SQL database, then converting project to 7.20 and start the runtime, in the ETM only the data of 7.11 is shown and the .ARX data before evacuation, but NOT the evacuated data of 7.20 ...