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 Authoring Displays
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Access Vision Displays By Name Instead of ID

When migrating displays from one environment to another using the Vision display utility there is no guarantee the ID will remain the same in the destination environment. Since Vision displays can only be linked to via ID, all links in both Vision and ProcessBook files would need to change. This significantly complicates the migration process and makes it very error-prone.
  • 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

  • rfesler
    Reply
    |     Dec 2, 2022

    we have a large amount of displays duplicated from the DCS so we do not have a way to automatically know what IDs are being chosed so we have to create a process (semi-automated) to map everything. if we could URL to just the display name instead of ID then we'd be able to make all this work without manual intervention and save lots of time. thank you!

  • jmjackson
    Reply
    |     Aug 19, 2022
    In addition to what has been mentioned, the ID number in the URL causes issues for users of Vision that want a quick way to change from one Display to another by altering the URL. In Processbook the navigation toolbar allowed users to change the name of the PDI file and open it quickly. For example, a plant with multiple generating units might have the same screen for different units with the only difference being a number in the screen name (1-Overview, 2-Overview, etc). So users could change the number and open the other units display quick and easily. Since Vision has the ID number in the URL the user cannot do this unless they know the ID number of the other display. Providing a way to navigate displays in Vision without the ID would allow for easier navigation and a user experience more similar to what was available in ProcessBook.