Summary

The project data synchronisation process in the Report Engine was fixed and now follows these steps (compare to predecessor bug):

• First, those items are synchronised in parallel with one task per item:
  • alarm/event classes
  • alarm/event group
  • users
  • equipment models
  • project metadata
• Then, the project contents are synchronised in parallel. Each project is synchronised in one task and each task processes those items in that order:
  • shift recording tables
  • variables
  • state lists
  • archives
• After the project contents, those items are synchronised in parallel with one task per item:
  • efficiency class models
  • sankey diagrams
  • waterfall models
  • all language tables (global project and each project content)

Description

The project data synchronisation process in the Report Engine was fixed and now follows these steps (compare to predecessor bug):

• First, those items are synchronised in parallel with one task per item:
  • alarm/event classes
  • alarm/event group
  • users
  • equipment models
  • project metadata
• Then, the project contents are synchronised in parallel. Each project is synchronised in one task and each task processes those items in that order:
  • shift recording tables
  • variables
  • state lists
  • archives
• After the project contents, those items are synchronised in parallel with one task per item:
  • efficiency class models
  • sankey diagrams
  • waterfall models
  • all language tables (global project and each project content)

Information

2 possible workarounds:

• Run the synchronization a second time from Engineering Studio - then the languages already exist and the error will no longer occur as no languages have to be inserted.
• Before metadata synchronization, create the required languages in Reporting Studio - then the languages already exist and the error will not occur as no languages have to be inserted.