Skip to Main Content
AVEVA™ Products 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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Status Reviewing
Portfolio area Enterprise SCADA Server
Products Realtime API/SDK
Created by Collin Heggerud
Created on Apr 8, 2024

Allow chained VDB field put overrides so integrators can override baseline fields

During development of some CIP functionality for [a customer], (EXT-417), we needed to trigger some protocol specific functionality when the "poll group" field changes. However, when we added a VDB override, it wasn't called. [R&D Architect] has confirmed that when a baseline VDB override exists, any additional overrides added are added lower in the table, and only the first override is called, so there is no way for us to achieve what we are trying to do. This will likely appear as a defect to [the original customer], so we will need to manage that and update this ticket with the outcome later.

Moreover, after Extensions overrides a field, it is possible another Extensions project, or a system integrator would also need to override the same field. So a chaining should be possible, or perhaps all field puts should be called. Consideration of this is required.

See attached for some background.

Expectation

Multiple VDB overrides for the same function should run one after the other, with a configureable ordering.

The subsequent overrides should be given the same arguments as the pre-existing overrides, with any input/output variables updated to the latest values from the previous override.

Might make sense to limit this to the types of overrides needed by those requesting it (mostly to do with protocols).

Idea business value

Allow integetrators to overide baseline functionality by using an extensibility method that currently is limited to a single extension.

Idea Type Improvement
Idea priority 4 – Important to my company
  • Attach files
  • Hugh Arai
    Aug 13, 2025

    The SE WWW group has also expressed interest in getting this functionality into the product.