Rename Sigmafine Entities
Background
Sigmafine displays are imported into SigmafineHub following the conversion of the original PI ProcessBook display into a format compatible with SigmafineHub (.inp file).
The conversion procedure creates a map of all display element names and their respective unique identifiers based on the PI Processbook display synchronization information.
Once the converted display is imported into SigmafineHub, this mapping enables SigmafineHub Visualizer to locate on which server, database and model the display is connected to, as well as locate display elements with the respective elements in the database.
Renaming Objects
Once a display has been imported into SigmafineHub, any rename performed in the original Sigmafine data structure leads to a malfunctioning of the SigmafineHub Display. This relates to rename operations performed on the Sigmafine database using third party tools (e.g., PI System Explorer).
Rename or Delete/Import Database or Model
Renaming the original Sigmafine database or model affects the opening of the display, as SigmafineHub will no longer be able to link to the original database and model to which the display refers.
The same happens if you delete your database or model and then you import it; although the entity name is the same, its unique id will be different.
Rename or Delete/Import Elements
When you rename of some of the Sigmafine database elements, it partially affects the display for only those renamed elements. The Display opens in any case, but some of the elements on the display loose the association with the respective renamed element in the database.
The same happens if you delete an element and then you import or redefine it; although the entity name is the same, its unique id will be different.
Corrective Actions
Any change performed in the original Sigmafine database, model or elements, requires a resynchronization of the original PI Processbook display, and the conversion and re-import of the modified PI Processbook display in SigmafineHub.