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.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

As an administrator, I would like to be able to backfill data that crosses over a versioning event

Use case: 1. An element has an attribute that looks up information on equipment configuration (ex: a pump rate) 2.  Due to an equipment change, the lookup table and the element were increased in version 3. A backfill needed to be performed on an analysis that included the attribute which changed, and the date range spans over multiple version effective dates. The desired behavior would be to use the latest version of the attribute's value since the last effective date, and the previous version of the attribute's value before the last effective date. 4.  Currently, the backfill cannot go further back than the effective date of the current version.
  • Attach files
  • Brent Bregenzer
    Reply
    |     Aug 20, 2022
    Hi, Cassie. For your specific use case, is it just the table lookup piece that is changing on the versioned element? I'm wondering if a workaround could be to include a datetime column for the effective dates in your table, and then the table lookup could utilize the "table provided time series data" setting to lookup the appropriate data based on date. This might allow you to avoid issues you've seen introduced by versioning.