Allow the PI Vision Display Utility to export the configuration to a file and import from a file
The current (2017) version of the PI Vision Display Utility requires both environments (source & target) to be connected. There is a need to be able to export and import those displays between systems that are not connected.
If not exported to a file, it could, for example, use PI Web API to use the REST endpoint to export the display configuration and vice-versa.
We are currently researching this item and evaluating it for a future release.
Odd, somehow this was turned into an idea. I originally had the link to the feedback item in the post, but i may have forgotten. Anyway, votes are better placed here: https://feedback.osisoft.com/forums/320517-pi-coresight/suggestions/18689953-exporting-and-importing-of-displays
Yes, I would think it shouldn't be too difficult to serialize the display information into a more transportable format (XML or JSON file) to move across different environments this way. I agree that the current functionality is very limited when working across segregated environments on different networks.
The CTP display copy tool is too limited. If we have a way to export & import displays in XML or Excel, that would allow for the proper maintenance, distribution, generation, version management, etc. of Coresight displays.
Now i need to manually build all displays MANUALLY 4 times when i push them through my environments from Dev, Test, Acceptance, Production. Environments are not on the same network, they can be local developer VM,s in different countries, different organisations, etc.