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.

Add a new idea Subscribe
Status No Status
Product AVEVA™ PI System Access (PSA)
Categories PI SQL Client
Created by Guest
Created on Aug 23, 2022

RELATED IDEAS

Include overridden attributes of derived templates in Event Frame View with PI SQL DAS (RTQP)

When you create a template-specific event view, event frames based on derived templates are also returned. However, attributes which are overridden in the derived template return empty. This means more complicated queries using UNION ALL must be used. As a user, when I use a derived template with an overridden attribute, it is often because I need to change the way that attribute is calculated in a subset of cases. However, I still want to be able to create a view easily for all of this data. For example, I have a "Batch" template with "Pounds Produced". However, for a specific case, the "Pounds Produced" calculation needs to be different. I still want to easily be able to create an event view for all my batches.
  • Attach files
  • Guest
    Reply
    |     Aug 23, 2022
    Any update on this?
  • Guest
    Reply
    |     Aug 23, 2022
    Using RTQP we are also facing this - derived templates are returning null values for overriden attributes... really not good enough. Tech support's suggestion is to use UNION ALL for every query, for each derived template.......seems like a major bug to me that needs to be fixed ASAP.
  • MarkGoepel
    Reply
    |     Aug 23, 2022
    We've hit this issue with Element Templates. Template inheritance is a powerful feature of AF, which prvides many benefits across the PI Platform. It is a pain that we have to treat the templates differently, even though it is a simple matter of for some element types the underlying tag in the control system is different across the different asset types. *No we are NOT going to mask the issue by moving the tagname override into the InstrumentTag... Can we please have this addressed with priority?
  • Guest
    Reply
    |     Aug 23, 2022
    Hi, is this in the engineering plan to be corrected in the next version of RTQP? One of the major benefits of PI AF is template inheritance; the fact OSIsoft has a product that doesn't cater for this to me seems like a major oversight.
  • Guest
    Reply
    |     Aug 23, 2022
    I found a workaround in the past, this was an issue with the PI OLEDB Enterprise provider also. The issue is the attribute has to be in the base template. So I created some hidden attributes in the base template just for reporting/SQL pointing on the original attribute. So these attributes don't get overriden and keep working in a query built on the base template.