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.

136 VOTE
Status No status
Categories Notifications
Created by Guest
Created on Aug 20, 2022

Referencing attributes on other Elements for PI Notifications 2016 Message

Request : Being able to show Attribute values from other Elements other than the attributes on the Referenced Element for the Message in Notification 2016. Description : From the old version, it was possible for a notification message to display a value not only the target element but also an attribute of other elements (by browsing down elements and selecting the attribute) In the 2016 version, it does not allow for the user to choose attributes in other elements but only the attributes of the Referenced (or targeted) Element. The screenshot (Attached file) shows a relative path of an attribute but this is when the user already had a notification rule on the previous version and migrated it. Newly created notification does not have this feature.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Another thing, it would be show attributes from child elements. Like, a rollup Notification.
  • DanielNeu
    Reply
    |
    Aug 20, 2022
    Our problem is that this worked in "older" versions and we have (had) a lot of notifications with this feature ! So for us it would be urgent to get this function back !
  • Guest
    Reply
    |
    Aug 20, 2022
    We started to receive complains about having that very used feature removed. The curious thing is that old PI Notifications grabbing child element attributes values are still working. So we just need kind of a "Add" button. !
  • Guest
    Reply
    |
    Aug 20, 2022
    We too have this issue. notification were still working after upgrade but unable to update the data reference in the notification when we made changes to our element hierarchy. Does any one have a work around for this? Only option I can think of is to duplicate all the required attributes from child elements in the reference element?
  • Guest
    Reply
    |
    Aug 20, 2022
    Need to put this back the way it was. As it is now. Notifications is worthless to me.
  • Guest
    Reply
    |
    Aug 20, 2022
    Our notifications broke after we upgraded to 2018 release. Please restore this feature asap.
  • Guest
    Reply
    |
    Aug 20, 2022
    Is this in the road map?
  • Christoph Rose
    Reply
    |
    Aug 20, 2022
    It would be very helpful if this would be supported in PI System Explorer again. As Ben Bohringer noted, it still works, it is just missing in the GUI of PI System Explorer. Using PI Builder, it is possible to manually edit the Delivery Format, and add attributes from other elements: Adding for example gets the Value at Start Time of the attribute "Attribute" in the sibling element "SiblingElement". The "ContentProperty" changes what property of the Attribute is selected (I couldn't find a list of what is what, but they can be gotten by looking at other DeliveryFormats). This is "simply" a GUI limitation for setting it up, Once correctly added via PI Builder, the attribute even shows up in the designer.
  • Guest
    Reply
    |
    Aug 20, 2022
    Some workarounds including Christoph are discussed in this knowledge article: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=How-to-reference-an-attribute-in-another-element-in-a-notification-email Note that Christoph's suggestion appears to work well, and based on some preliminary testing and verification we don't anticipate any issues. That being said, since the feature was never fully tested, there are no guarantees from OSIsoft. Be mindful that the path relative to the target element has to be used.
  • +36