Copy or migrate displays between systems & reassign data items
Be able to copy displays between different Coresight systems. One example might be a dev --> test --> prod scenario. The migration needs to include the reassigning of data items to a new PI-AF server and/or PI Server.
But there are other cases where you want to reuse a display that's already been created but it's in a different Coresight system.
Note: This was previously Enhancement 64766.
The PI Vision Display Utility was released with PI Vision 2017 and allows PI Vision administrators to move displays between PI Vision servers and update data items on displays to facilitate migration between development, test and production environments.
Some feedback on the current tool: environments might not be connected, so a copy between databases wont work for me for most of our customers.
If we are able export to a datafile, and import on the target server, that would be useful.
What we actually want is a manner to export the display definition, like one can with AF libraries and element trees, or Process Book dashboard designs. Such a feature will allow version control and formal configuration management on display designs, by putting the export file under version control.
I strongly suggest OSIsoft begin to regard at least the power users of their products as professional system integrators and software developers, who follow formal configuration management (change management) principals. Such users rightly expect products that support such practices.
there is a way with the Chrome browser to copy one or many symbols and graphical objects from one display to another.
Just open two PI Coresight sessions with the displays in question in separate tabs and set both in design mode.
Then mark objects in the first display and copy and paste them to the second display.
Does not work well in IE11 though.
I just stumbled into an issue where we changed one element name in the AF path for attributes used in a Coresight display and it broke the display. The Tech Support engineer reported this is a design issue in that there is no means to have the path correct itself the way renaming a PI tag can. He suggested this as the possible fix. So I guess I am voting for this - but to be honest I consider this a huge 'thud' for Coresight...
it think it would be genereal a good idea to have an export / import function (xml) through maybe powershell
- then you also can convert displays from other suppliers and import them
- migration scenarios
- use it for a tool who mass creates some displays
This is a priority request for a few of my clients as well, to manage migrations through environments.
Prio 1 for me. Event if it's a simple serialize to XML and back of the data structure or something like that. The tools for supporting the promotion to different environments can be built relatively easy.
i am agree to have this new feature