Potential loss of project documentation, extended properties, and custom properties
Project documentation, extended properties, and custom properties—collectively called optional properties—add valuable information to projects. When you download a project to a controller, you can choose not to download these optional properties with the project.
However, when you do not download the optional properties with a project there is a risk of losing the information if a second workstation attaches to the controller after you download the project. On the second workstation, the project appears to be synchronized but it is not.
The following situations could lead to a loss of project documentation, extended properties, and custom properties:
Situation | Example |
If optional properties are not downloaded to a controller, they cannot be uploaded. | The user on workstation 1 downloads to the controller a project without its optional properties. If the user on a second workstation uploads the project file, there will be no optional properties in the project. |
Optional properties are not synced across multiple workstations. | The user on workstation 1 downloads to the controller a project without its optional properties. The user on workstation 2 goes online with the same project file and it successfully correlates, but it does not contain any optional properties. If the user on either workstation changes the optional properties, the projects on the workstations will contain different data that cannot be correlated. |
The user on workstation 1 downloads to the controller a project without its optional properties. If the user on workstation 2 makes online edits to a routine or logic that does not contain optional properties, the optional properties associated with the routine or its logic is deleted when the user on workstation 1 finalizes the changes. | |
Source Protection does not prevent potential loss of optional properties. | Workstation 1 has a source-protected routine or Add-On Instruction (AOI) that has optional properties in the logic. The user on workstation 1 downloads to the controller a project without its optional properties. The user on workstation 2 uploads the project to a new project file. The project uploads with no warnings or errors, and the routine or AOI does not have optional properties. |
If optional properties for signed or sealed Add-On Instructions are not downloaded to a controller, they cannot be uploaded. | Workstation 1 has a signed Add-On Instruction (AOI) that has optional properties. The user on workstation 1 downloads to the controller the project without its optional properties. The user on workstation 2 uploads the project to a new project file. The controller displays the following warning:
WARNING:
<AOI Name>: Sealed protection has been compromised. The warning indicates that the AOI signature does not match the original AOI because the optional properties changed. |
Provide Feedback