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

Status Declined
Categories Navigation
Created by Guest
Created on Aug 19, 2022

Do not preserve old values in Gauges or values

I designed a display. I wanted all of the parameters shown to be from a different set of assets. (URL parameters didn't work because they were in an AF hierarchy nd not a flat structure). I draged the numbers onto the guages and values and viola, the values reflected the new, dragged on value. The issue is that when you clisk on the value and view the history, it still shows the original value and there is no way to get rid of the original. Would be best if the oroginal disappeared, but secondarily, make it possible to delete the original.
  • ADMIN RESPONSE
    Aug 19, 2022
    Thanks for sharing details and clarifying this request. When updating a value symbol, dragging a new attribute will update the symbol value but not the multi-state as the multi-state is configured independently. You will need to drag the same attribute to the multi-state area as well. There are no near term plans to implement the requested functionality.
  • Attach files
  • Guest
    Reply
    |
    Aug 19, 2022
    I realize what the problem here is, and so am changing it. The reason the old values were being preserved is because that other value was being used for the multi state. I think, then, that the suggestion is, that when I drag a new attribute onto a value that I have formatted in a certain way, the value and the multistate should both be updated to reference the new attribute (especially if the value and the multistate used to reference the same attribute previously).