PI Vision navigation
Synchronise Navigation Menu+ across PI Vision displays by storing one shared menu configuration in an AF attribute.
When a PI Vision application contains many displays, a consistent navigation experience matters. Navigation Menu+ can save its configuration to a shared data source so the same menu can be reused across displays. Update the menu once, and every display that points to the same configuration store can load the shared structure.
The configuration pattern
Create one string AF attribute as the configuration store. Add Navigation Menu+ to a display, point its save configuration to that attribute, and reuse the same attribute wherever the menu should stay synchronized.
What you need before starting
An AF element
Choose the element where the shared configuration attribute should live. Use an element that is available to the people and displays that need the menu.
A string attribute
Create a string AF attribute. Its value stores the menu configuration, so give it a clear name and apply the permissions required by your operating model.
Navigation Menu+
Add the symbol to a PI Vision display and decide which display will be the initial source for the menu structure.
Configure the shared navigation menu
Validate synchronization
Test the workflow with a small menu change before rolling it out broadly. The goal is to confirm that the source display writes the configuration and that another display can read the updated value.
- Open two displays that use the same AF attribute.
- Change one menu label or add one test item on the source display.
- Save the display and allow the configuration to be written.
- Refresh or reopen the second display and confirm the change is present.
- Remove the test item and repeat the check with the final structure.
Use separate menus when workflows differ
Synchronization is useful when displays belong to one application or role-based navigation model. It is not necessary to force every display into the same menu. If two areas need different navigation, create a second string attribute and use it as the configuration store for that menu.
One shared attribute
Use this when the same menu should appear across an operator area, a report area, or a linked set of displays.
Separate attributes
Use different stores when sites, roles, or workflows need independent menu structures and ownership.
Clear ownership
Document who can change the source menu and how changes are tested before they reach production displays.
Troubleshooting checklist
- Menu does not update: verify that both symbols reference the exact same AF attribute.
- Changes disappear: confirm that Save Configuration is set to Datasource and that the user can write the attribute.
- Items point to the wrong display: review the saved links and test from the target user’s permissions.
- Different teams need different menus: create another configuration attribute rather than editing the shared one.
Once the test passes, reuse the configuration store across the displays that belong to the same navigation model. This keeps the PI Vision experience consistent while preserving a clean separation between independent workflows.
Keep PI Vision navigation consistent
Use Navigation Menu+ to create a maintainable shared navigation experience across your displays.
Explore Vision Library+

the picture details from your support article “Synchronise Navigation Menu across displays” have been stripped from web viewing..
Been having issues with this, and wanted to see what tricks you documented… but hard to follow without your attached screen captures.