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 Integration / URL Parameters
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Allow ?Asset= to use all the derived templates under a base template as correct matches

Attempting to use the parameters reference to reuse a display using the ?Asset= approach. All my assets at one level are based on the the same template with a couple of them derived from that template. This approach seems to require the template to be an exact match and not derived from the same template - is that the case? It would be far more useful to me if I could build one display based on the "building dashboard" template and then use it on that template and all derived templates as they will have the same "base" attributes. Yes I know you can exclude but just not displaying that value would be better in my view. Maybe it's an enhancement request.
  • ADMIN RESPONSE
    Aug 19, 2022
    Enhancements to the Asset= parameter in PI Vision 2017 allow for the use of assets from derived templates of a PI Vision display. In addition, PI Vision 2017 R2 introduced the ability to configure the asset template, asset category or asset name filter used for the asset selector on a display.
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    We have setup assets based on a set of LIKE templates Transformer_Base Transformer_Base+loading Transformer_Base+XY_Prot Transformer_Base+XY_extended Transformer_Base+XY_extended-2 These are all transformers and in the Transformer group and should all be visible in the ASSET view. Otherwise this negates the usefulness of the parent child hierarchy.