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
Created by Guest
Created on Aug 20, 2022

Be able to disable auto backfilling on a per analysis basis

Currently in the analysis service configuration there is a parameter called “AutoBackfillingEnabled” which affects the analysis calculations in a global basis. It would be great if it were possible to disable the auto backfilling to individual calculations.
  • Attach files
  • caffreys_col
    Reply
    |
    Nov 22, 2024

    We have many analysis where backfilling is not required. The attribute we link the analysis to is only for information purposes (instantaneous data) which is not required to be reorded in the historian. Whenever we check the AF system for errors we always see the "requires mapped output to be configured"even though we know it's not an error we need to fix.

  • Guest
    Reply
    |
    Aug 20, 2022
    The correct name for this parameter is AutoBackfillingEnabled. The term "EnableAutoBackFilling" was improperly used in case # 800600.
  • Guest
    Reply
    |
    Aug 20, 2022
    Please refer to idea: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/19642603-be-able-to-disable-auto-backfilling-on-a-per-analy
  • Guest
    Reply
    |
    Aug 20, 2022
    I have some analyses mapped to attributes which have no history output saved, Auto Backfillings always give unecessary errors for the analyses.
  • Guest
    Reply
    |
    Aug 20, 2022
    In my case, I'd like PI Points that are output of an analysis to also be source tags for OPC output PI Points. When backfill of the analysis occurs, it triggers writes to the PLCs with unwanted old data. Since automatic backfill for other analysis is desired, we'll need to develop some other solution. In some integration solutions we've worked with, where external systems receive PI data, backfilled data is not desired. So having the flexibility to disable backfill for specific analysis would open up more "off the shelf" possibilities involving PI AF.
  • Guest
    Reply
    |
    Aug 20, 2022
    Same need as Jackie Li (Comment from Vendredi 26 octobre 2018). My need is to beabble to flag "Backfillable" analysis. Means I can choose the analyses I want to integrate into the AutomaticBackfilling.
  • Shawn McNabb
    Reply
    |
    Aug 20, 2022
    Also same issue as Jackie Li and PDUHAMEL. We have some analysis that don't need history. This makes O&M more difficult because we always see errors. It would be better to have the ability to choose which analysis participate in backfill.
  • Marco Blokdijk
    Reply
    |
    Aug 20, 2022
    It whould be really create if you can adjust this per analysis. I'm using a custom datareference to trigger the analysis (nothing special for the analysis). This CDR will only trigger the analysis when all inputdata is available for a certain output timestamp. The CDR can control the backfilling by itself (gap between last output and progression of the inputs). This works really great, but only if I switch of the AutoBackfilling setting. Yes please, make this adjustable on a per analysis basis!