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 Declined
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Add support in AF Clients for changes to a single timestamped value in an external system brought into AF using a linked table

A table in an external system (SQL, Oracle, etc...) has a single entry that may change from time to time. When this entry changes, it should be picked up automatically by the PI Analysis Service without an extra "No Data" event. Currently there are some workarounds: 1. Use a PI Point instead of a linked table. 2. Use a static attribute instead of a linked table. 3. Add an extra event in the table at 1-Jan-1970 4. If another PI Point or static attribute updates at the same time as the data in the external system, remove the time context from the table lookup data reference and use this PI Point to trigger the analyses.
  • ADMIN RESPONSE
    Aug 19, 2022
    For this configuration, the external table is being used as "time series" data which comes with it some limitations. One of those limitations is that two values are required in order to interpolate. In the case of an external table such as this example which only has 1 row, it breaks the assumptions for time series data since the only way to get two values is to assume one value as NoData and the other value being the actual value (table row). As such, there is no plan to make any changes to accommodate this use case, which does not fit into the assumption of time series data. As noted, there are several workarounds that may be considered.
  • Attach files