Cascade Changes

Changes can be cascaded through to all associated references within the Grid Editor.

For example, if you change the cluster or tag name for a variable, any alarms or expressions that reference the variable as a trigger will also be updated with the new name.

Clusters context is a key determinant for changes being cascaded. When you change a tag name, the cluster associated with it will be used as a filter, and changes will be cascaded to alarms or expressions for that cluster only. If a cluster is not defined for a tag, the cluster name will be determined by the cluster specified for the associated I/O device, or the I/O server if the I/O device does not have a cluster specified. If you change the name of an I/O device in the grid, the cluster name of linked I/O server will be used for cascading changes to linked references.

Plant SCADA does not consider case sensitivity when it determines what needs to be changed.

Cascading changes are not supported for the following:

• Labels, groups, equipment states and remapping

• Alarm categories

• Equiment.item references used in expressions.

  Note: Cascading changes are only passed through to associated references within the Grid Editor. References that occur in locations such as graphics pages and Cicode files will not be automatically updated. Changes will not be cascaded if grid data is manipulated externally, for example through a tag import or modifications made through the Equipment Editor.

To cascade changes on update:

1. Open the Options dialog from the Activity Bar.

2. Set the Cascade changes across the system option to Always.

To disable cascading changes:

3. Open the Options dialog from the Activity Bar.

4. Set the Cascade changes across the system option to Never.

To receive a message before you cascade changes:

5. Open the Options dialog from the Activity Bar.

6. Set the Cascade changes across the system option to Prompt.

If you select the Prompt option, the following message will be displayed when you save your changes.

• Click Save & cascade to save the change and update the field value across the system.

  Note: Details of unsuccessful cascaded changes are logged in a Change Log, which is located in the %PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Logs\ChangeLogs. A cascading change may be unsuccessful if you update a field with a value that exceeds the maximum number of characters the field can hold, if duplicated tag references occur, or if the database file that needs to be updated is inaccessible.

• Click Save only if you want to save the updated field value for the current view only.

• Click Cancel to stay in the same view without saving your changes. The changes you have made will continue to be displayed.

• Select the Remember my preference option to automatically use the currently selected option for subsequent save operations. Whenever required, you can switch to a different option using the Options window.

  Note: Changes that are cascaded across the system are not applied to system projects.

See Also

The Grid Editor

Save Changes

Edit Values in the Grid Editor

Edit Values in the Property Grid

Edit Multiple Values