Event Frame Template Child Attributes in PI Vision

I spent allot of time working on organizing data in an event frame template. Part of this was to place child attributes under a parent.

As an example, I may be capturing a value that has other useful data like a limit or a forecast. Maybe an average, min, max... It makes sense to me to display some of this data as a child attribute. So I set this up in the event frame template.

Once I completed organizing the data and tested the event frames, I noticed that PI Vision will not display children attributes in the event frames. I also noticed that PI Vision can’t even show categories. I'm struggling with understanding why these features are available in System Explorer, but not able to be seen or used in PI Vision (the tool we want users to see data in)?

I think it's too bad that a user can’t properly see what all is captured in an event frame if you use child attributes within PI Vision.

  • I presume that you are talking about the Event Frame table, as you can see that data on the Event Frame page itself via Vision. I agree that it would be nice to see non-standard attributes on the table as well though. You can build a custom symbol using the existing symbol though.

     

    There is a feedback item that has not been addressed which covers many topics, but includes your item as well. Event Frames Table & Features | AVEVATm PI SystemTm Feedback Portal

  • The event frame table, or the link you click within vision to see the event frame data, does not show child attributes at all. You can only see them captured in the event frame within system explorer. So bassically the data is captured in the event frame, but not viewable to users within PI Vision.

  • I re-read your comment to clarify, and yes, that is correct. Sub-attributes of an attribute on an Event Frame are not displayed on the Event Details page. I'm not sure why they would not be captured in displaying the Event Details, but I've typically kept EF templates as a flat structure.

     

    A custom Event Frame table would be the best solution to view the data as it would be the easiest to replicate as you already have the source code (as compared to building a custom application to view events). It's still going to be a challenge, even in copying the JS & HTML directly from the existing EF Table symbol to add displaying the custom columns. It's possible, but it would take some work.