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 PI Integrators
Categories AVEVA™ PI Integrator for Business Analytics
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

Provide support for automatic updates for PI data in Event Views

There are automatic updates for PI data in Asset Views and Streaming Views, but not currently in Event Views which is what's used for Event Frames. This is important for propagating changes in EFs Use case example: GADS classification. Data comes in and EFs are created. The integrator picks this up and sends the info along. Some time later (maybe a few days / maybe month end) data comes in re-classifying / updating the original data (ex. GADS code or attributes). In order to accommodate this manual intervention using the "Update Data" button is required.
  • Attach files
  • Nuno Carvalho
    Nov 5, 2026

    We are using PI Integrator for Business Analytics 2020 R2 SP1. An Event View named IMBS_Eventos is configured to publish to Microsoft SQL Server every hour.

    The scheduled publications run successfully and write rows to the SQL table. However, when an Event Frame that has already been published is subsequently modified in PI AF, those changes are not reflected in SQL during subsequent scheduled runs.

    For example, users may correct the cause, classification or comments of a stoppage after it has ended and been published. These corrections normally occur within seven days of the event ending.

    If we manually select “Update Data” and reprocess the relevant time range, the changes are correctly reflected in the SQL table. Also if we refresh "Update Data" with a frequency of 1 min for a short period also the SQL is not updated.

    The attached logs show successful hourly publications and a subsequent manual backfill. No errors are reported in those executions.

    Reply