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 Declined
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Have AF PI Point attributes that reference another AF attribute use the retrieval methods of that attribute

When an AF PI Point attributes references another AF attribute that has  RelativeTime, TimeMethod, or TimeRangeMethod set, use the settings of the referenced  attribute. For example: Attribute A references PI tag B with a RelativeTime of -1h. Attribute C referencing attribute A will give the value of B at the query time, not offset by -1h.
  • ADMIN RESPONSE
    Aug 19, 2022
    Declined due to backwards compatibility concerns.
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    As I downvoted this, I believe I owe it to the OP as to my reason: this would produce breaking code in my applications.  I frequently use relative attribute references with the PIPoint DR, and I specifically do so for different TimeRangeMethod, etc.  Oftentimes I have many static string attributes used to compose the name of a long tag name, and a relative reference makes this easier to maintain.
  • Guest
    Reply
    |     Aug 19, 2022
    As Rick mentioned, this breaks existing applications. The purpose of the attribute reference option in the PI Point Data Reference is to keep from having to re-specify tags in multiple attributes when different methods are needed for the same point. Perhaps the feature you are looking for is something we refer to as Attribute Aliasing (not yet implemented) - which allows you to specify to use a different attribute as the source for the value.