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 No Status
Categories Event Frames (EF)
Created by Guest
Created on Aug 20, 2022

Additional documentation and examples to reference non-primary referenced Elements on Event Frames Templates

Some users asked for an enhancement of the documentation/ guide videos regarding syntax for referencing a non-primary element on a PI Point attribute from Event frame templates. The OSIsoft live guide does not provide enough information and/or examples about this and may lead to confusion. As an example, one customer wanted to create an attribute on an Event Frame Template referencing a Pi point attribute belonging to a non-primary reference element at the same level as the primary element on the AF elements hierarchy. In order to do this, it is necessary to use the following syntax and logic: .\Elements[.]\..\.\[@Name = ]| This sets the start as the primary element, .\Elements[.], moves up one level, \..\, then down a level and chooses the non-primary reference element by using the syntax .\[@Name = ]. In that element, you proceed to reference an attribute as follows: |
  • Attach files
  • BradR
    Aug 20, 2022
    All documentation referencing event frames needs improvement. Regarding tis enhancement request, referencing attributes in parent and child elements is confusing. I've called in and had tech support struggle with this. Needs much work in documentation.