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
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Add support for multiple events with same timestamp in PI Integrator for BA

The Integrator for BA appears to be a great fit for exporting event-based data such as Batch Interface Messages to external systems. Interpolation doesn’t apply in these cases so we can use a tag as the ‘Key’ in value mode selection. However, there are cases where a tag can have multiple entries at a given timestamp (e.g. EMDVB Recipe Parameter Downloads) and the current behavior is to only include the first value in the output view. This approach results in missing data and makes the integrator unusable in these cases. Ideally the view would return all records (as per PI OLEDB) or provide a selection to allow the user decide how it should behave
  • Attach files
  • Thomas Schnoor
    Reply
    |
    Sep 13, 2022

    Please please please fix this!!!

  • Kraus
    Reply
    |
    Aug 16, 2022
    A business integrator, which is not able to export all of my data if needed. That is a bug and not a feature request. Please fix...
  • Guest
    Reply
    |
    Aug 16, 2022
    As Kraus has stated, this is not a feature request. It's a fundamental flaw of the PI Integrator that needs to be fixed.
  • Kelsey Bobeck
    Reply
    |
    Aug 16, 2022
    This has been an outstanding *bug* for over three years. We need this fixed immediately.