Skip to Main Content
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.

Status Declined
Created by Guest
Created on Aug 19, 2022

Add an option to mark the PI Point Data Reference to not be updated when a Create or Update data Reference is issued

Currently when a PI Point Data Reference receives a call telling to Create or Update the Data Reference, it will resolve the String builder and then lock that Data Reference so that if someone changes the template, that change will not be replicated to the tags already created and a "Reset to template" is required for it to get the new tag naming. I understand that this is a way to speed up the system but that brings two issues: 1) On some cases if you created a tag and it already have value you don't want to rename the data reference as you would lose the link to the tag. (AF could also find the change and rename the tag accordingly) 2) We lose the capability of dynamically changing the tag names based on AF Attributes. For example, in our case we have two tags: pH_Hi_ProgramA pH_Hi_ProgramB And we have an attribute that will tell which program we are associated with (Program A or B). So, if we do not use the Create and Update Data reference, when we change from Program A to Program B, the attribute would point to the correct tag. But after we use the Create and Update Data Reference, the tag name would be locked and in order for it to change we need to issue a Reset to Template. I understand that a solution for our problem would be just not use the Create or Update Data Reference on the asset level and only use it in the points that require it, but there's no way (that I know) to enforce that. So, ideally, we would want to mark those attributes to never be "locked" by the create and update data reference.
  • ADMIN RESPONSE
    Aug 19, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    @wilson.laizo If I understand point 2 correctly, you could create two PI Point attributes that reference each tag name and then create a third PI Point attribute that dynamically references the other two attributes, e.g. if the two attributes are called pH_Hi_ProgramA and pH_Hi_ProgramB, the third dynamic attribute would point to the attribute |pH_Hi_Program%@AorB%. The substitution parameter used in the third attribute will not be resolved (or locked). Only PI Point attributes that reference tag names are resolved.