Support renaming of AF elements and attributes
PI Vision does not support the renaming of AF elements or attributes or the movement of them within the hierarchy. After renaming or moving these objects, symbols referencing them will show No Data in PI Vision.
We are currently researching this item and evaluating it for a future release.
Seth Sauder commented
In response to brian roberts, "two questions ....1) is the script avail..."
#1: Yes, I will contact you directly to share the script.
#2: In most cases there will be no issue with PI Points since the name and PointID are both stored in the definition of the display. A tag rename is handled automatically. A tag deletion and re-creation will also work fine, if that is what "retagged" is referencing.
two questions ....1) is the script available for AF item moves that "break" PI Vision references? 2) does the script or other script work for PI Vision references to PI Points that have been renamed/retagged. thanks.
We run several open pits. Part of our daily business is the adaptation of plant names to the progress of open pits. Facilities are being built, relocated and taken out of service. Each of these actions requires changes in PI-AF and PI-Vision. Most of these are renaming of the plants to depict the progress of mining. A simple way to rename elements in PI-AF and at the same time in their dependent PI-Vision displays would save us a considerable amount of time.
This is a major issue as it blunts much of the flexibility built into AF and Vision. We have a use case where AF Elements can move to other spots in the hierarchy on a regular basis.
Also, PI Vision 4.x is NOT this release scheduled for Q2 2019, correct?
So it should take even longer?
will other clients also support the renaming of elements?
I am now particularly interested in the PI Integrator for Business Analytics.
Vincent Kaufmann commented
Hi Alan, please see this request.
PI vision symbols mapping to the AF attribute through the address path string. That data connection will "break" if any of the elements in the path are changed or relocated. If PI vision mapped to the attribute value using the attribute and element unique IDs the PI vision display could be resilient to any changes in the AF naming or hierarchy.
I have Changed the root Element & created new Elements. But in PI Vision all old elements are showing up with "No Data" status when placed on the display.
Getting this fixed potentially has huge benefits in areas such as Pharma where Coresight screens may be a controlled part of a process, which in turn locks down the AF model and takes away most of the flexibility of working with and editing a tree-structure model. Any steps that can be taken by OSIsoft to make sure the AF elements and attributes can be moved around without breaking the data connections to the tools that use them (coresight, notifications, analytics, etc) is a huge plus!
If you change the root element of AF structure, all your displays are automatically broken!
Just found out this is an issue.... an a big one if you have lots of displays and frequent rebuilds of the AF model...