AVEVA™ PI System™ Feedback Portal

Welcome to our 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 Completed
Product AVEVA™ PI Vision™
Categories Navigation
Created by Asle Frantzen
Created on Aug 19, 2022

RELATED IDEAS

Better control of what is shown in Switch Asset List

When designing displays I would like to control how much of an element's path is shown in the Switch Asset dropdown. I've found myself in the situation described by this thread too many times: https://pisquare.osisoft.com/thread/34664-asset-framework-naming-for-pi-vision I would like to be able to control how much of the path is displayed in the name of each asset, for example like the "Data item length" slider available in the PI DataLink search dialog. In the PISquare thread above the asset (RTU) can only be identified by including part of the path (Station1\RTU).
  • ADMIN RESPONSE
    Aug 19, 2022
    PI Vision 2021 introduces new capabilities that allow users to show a partial asset path in the asset list. See an overview of new PI Vision 2021 capabilities on our YouTube learning channel: https://youtu.be/LomuqXKEH7w For additional information on PI Vision 2021, please see the release announcement here: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000037703
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    This should be configurable by the user. If the path is very long it will make this very messy
  • Jason Gogal
    Reply
    |     Aug 19, 2022
    Even better would be to be able to alias the element. I see situations where the path name is not what it would be best to show on the display.
  • Guest
    Reply
    |     Aug 19, 2022
    I agree we need the ability to show parent elements. I have hundreds of elements using a template so i had to simplify by organize them under a location parent element. Now the drop down (without showing the parent location) does not show enough information to select different assets
  • Guest
    Reply
    |     Aug 19, 2022
    Asset drop-down menu should show the full path of the element (not only the element name). In case we have two child elements with same name coming from different parents,  it might be confusing to differentiate between both duplicated element unless you hover over the element name to get the whole path (hierarchy) as shown below.
  • Daniel Imperiale
    Reply
    |     Aug 19, 2022
    You may already know this but for those that don't, this feature is available in PI Processbook AF Relative displays. That is my workaround right now.
  • Guest
    Reply
    |     Aug 19, 2022
    This should be configurable. For instance, the element description or a certain attributes value could be shown in the list instead of the element name (or path).
  • Guest
    Reply
    |     Aug 19, 2022
    I have a use case where the final elements in a hierarchy all have similar names. there are a bunch of 1A, 2A, and things like that which require additional path information to differentiate them. It is undesirable to rename these elements. The path is available if the user hovers over the item, but that takes to much time to enable effective navigation. The option to display the path in the list would alleviate this problem. The attached screenshot shows the issue.
  • Guest
    Reply
    |     Aug 19, 2022
    Having the ability to switch context based on element description vs. element name I feel would resolve a lot of issues. I have the same scenario that Robert mentions below. Multiple assets with the same name at different locations.