AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No Status
Product AVEVA™ PI Vision™
Categories Display Management / Displays Page
Created by Guest
Created on Aug 18, 2022

RELATED IDEAS

Display Utility options for duplicate displays

I would like the PI Vision Display Utility to give me a warning and options if I try to move displays to a target database that has existing displays with the same names. This would avoid unintentionally creating duplicate displays with the same name. It might also be useful if the tool gave me options in this case such as: 1) Acknowledge the warning and create the duplicate displays 2) Rename the new displays before adding them to the target database so  that they are no longer duplicate names 3) Overwrite the existing target database's displays with the new displays and keep the original target display's DisplayID.
  • Attach files
  • MarkGoepel
    Reply
    |     Mar 4, 2024

    We are increasingly embedding more an more Native PI Vision (not PB) displays in other applications.

    These displays are maintained by end users, and through one reason or another, the DisplayID invariably changes.

    This means we need to touch all the applications to update to the "new" version of the display, because the URL changes, even though the display name does not.

    This is very annoying

  • Guest
    Reply
    |     Aug 18, 2022
    These options would be of particular importance in an environment like ours, where development work is done on one Vision server, and the finalized results promoted to a separate, more heavily-protected Vision server, intended for "official" reports and displays that must be protected from accidental or unauthorized modification. Currently, attempting to modify an existing page in the "dev" server then promote it to the "prod" server results in duplicate displays with identical names. In the interim, a SQL script to re-name or re-number displays would be helpful.
  • Guest
    Reply
    |     Aug 18, 2022
    Please can someone from OSIsoft confirm if these issues with display utility will be sorted out in next version of PI Vision ? One of our clients has test and Production PI Vision environment and we are having issues with duplicate displays when transferring from test to Production environment. It would be better to get this sorted before next version roll out so that we can convince the client to upgrade it.
  • Ryan McErlean
    Reply
    |     Aug 18, 2022
    This behavior has not been changed in the PI Vision 2019 release. The PI Vision Display Utility does currently support overwriting when copying displays between servers, however, in order to overwrite it requires that the display name and display ID be identical on both servers. This is only possible if the production system SQL database was created from a backup of the test system SQL database (or vice versa). We understand that this is a significant limitation and will be considering ways to address this. This item will be updated if there is a change in status.
  • Guest
    Reply
    |     Aug 18, 2022
    Makes you wonder how OSIsoft handles their SDLC process when making updates to their software. Having to make manual changes on a production PI Vision display that has high visibility production data out on the manufacturing floor is precarious at best. This is like people including a revision number in their file name of a Word document and sending out a link that gets broken when the next revision to the document is made. Maybe I'm just not understanding what OSIsoft engineers had in mind when originally developing PI Vision.