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.

Created by Geoffrey Coad
Created on Feb 16, 2022

Prevent a composition from being added to a Class Library if it has a conflict with exisiting data

We recieved this issue from Eugene Khoo, Aveva Service Delivery for Shell: https://dev.azure.com/AVEVA-VSTS/Information%20Management/_workitems/edit/1757181

It was determined that the problem was caused by an Extension Namespace conflict where the class library being added to the the composition had an Extension Namespace with an identical url but different prefix (the nmcltr namespace had had the prefix changed) whislt the user was provided a warning in the UI it the deleted all the compositions and the Extrension Namespaces (See attachments)

The suggested idea is: where this scenario happens the Composite Class library is not allowed to be added, with a relevant UI message but leaves the class Libary unchanged rather than trying to fix/delete the conflicted items


  • Attach files