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 19, 2022

AF enumeration sets should support values with the same name

The feature introduced in 2018 SP2 to manually synchronize digital state sets with AF enumeration sets has a limitation where state sets with duplicated names aren't imported correctly into AF. This is due to the current design of AF enumeration sets that don't allow duplicated names for enumeration values. It would be nice if AF enumeration sets supported multiple values with the same name as it is supported in digital state sets in the Data Archive.
  • Attach files
  • Kelsey Bobeck
    Reply
    |
    Sep 10, 2024

    This is presenting quite a problem for me currently. I'm trying to replicate a digital set, but two of my values (14 and 15) are "BAD" and no matter what I do (change case, add spaces before/after), it won't let me check in both of them. I don't understand why it was setup this way. There's already a unique key (the integer value), so why require the name to be unique too?