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 Completed
Product PI Connectors
Categories PI System Connector
Created by Guest
Created on Aug 20, 2022

PI System Connector should be able to delete values on the destination server if they are deleted on the source server

Sometimes when performing analysis recalculations, values are dropped from when they were initially recalculated. For example, when an analysis runs initially, it may calculate 15 values, which are then written to the source and transferred over to the destination as expected. However, if I perform a recalculation where I choose to permanently delete existing values and recalculate due to some of the analysis inputs having changed, and only 10 values are now written to the source server, these values are written to the destination, but the existing values that are now "incorrect" are still present. I would like for the System Connector to see that the events have been deleted in this instance on the source server and delete the same events on the destination.
  • ADMIN RESPONSE
    Aug 20, 2022
    Support for Append and Delete write behaviors are now supported with PI System Connector version 2.5.0.1. In order to take advantage of this new feature PI Connector Relay 2.7.0.8 is required.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Manual deletion of the calculated results on the destination system is a good workaround for small numbers of tags, but is impractical for larger analyses
  • Guest
    Reply
    |
    Aug 20, 2022
    Ability to have deletions replicated across systems as well (might need to be a config option on how to handle).
  • Guest
    Reply
    |
    Aug 20, 2022
    I would assume most companies have a source and destination PI collective. I feel like I'm always asking for the same thing. We need them in sync. If our analytics are running on the source system (and AF) and we change an analytic calculation, the data is only corrected on the source side. The destination side is now wrong and has bad data! This leaves us a mess to try to clean up! When we change an analytic on the source side, and recalculate and replace the data the same needs to occur on the destination.
  • FranzK
    Reply
    |
    Aug 20, 2022
    How about the state of this request? This request might help to ensure data quality. As deleting data should be handled carefully, i agree with Todd to make it configureable at least at the connector level (maybe even more granular e.g. based on the local point source or other point attributes).