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 Jose Sanchez Colunga
Created on Aug 19, 2022

Possibility to disable the message "An AFEnumerationSet matching the digital state set for PI Point was not found" in PI System Explorer

I would like to have the option to disable the feature introduced in PI System Explorer 2018 SP2 to pop up the following message when an Enumeration set does not match the name of a digital set in the PI Data Archive: "An AFEnumerationSet matching the digital state set for PI Point was not found" The message appears every time you open a new element with attributes with not matching Enumeration sets for each of those attributes.This can become very tiresome.
  • Attach files
  • Kelsey Bobeck
    Reply
    |
    Oct 2, 2024

    This happens when the names of the enumeration set and the digital state set don't match. For example, I have a tag with a Digital State set called [Site Code].A/B/C/D/E/F/G with the values mapped A-G, 0-6. This exists for six sites. In AF, I created a more generic Enumeration Set called "Stability Class", still mapped A-G, 0-6. Every time I expand an attribute (I have these set as a child attribute) or search, I get 20 pop-ups telling me "EnumerationSet Not Found" and it's incredibly frustrating, as this is not the only attribute with an Enumeration Set like this.

  • Guest
    Reply
    |
    Aug 19, 2022
    We're having trouble understanding what you're doing. How many different missing Enumeration sets do you have? Can you provide some examples of your use case - i.e. step of step of what you're doing?
  • Guest
    Reply
    |
    Aug 19, 2022
    This message appears for AF attributes which are mapped to a digital PI tag with a digital set in the data archive but not in AF. It's annoying as the same question is asked for the same attributes each time even though the answer was already provided.  
  • Guest
    Reply
    |
    Aug 19, 2022
    In response to Dogan Saglam, "This message appears for AF attributes w..." Are you binding each of the attributes to the same PI point that has the missing digital state set? Or, does each attribute point to a different PI point with an undefined digital state set?   If it's the same PI point for each attribute or different PI points also pointing to the missing digital state set, then you could answer yes to create the digital state set and modify it later once your attribute editing is complete.
  • Guest
    Reply
    |
    Aug 19, 2022
    Each attribute is pointing to a different tag with a defined digital state set.
  • Guest
    Reply
    |
    Aug 19, 2022
    After further examination it's been determined that this is an issue. The question is being asked regardless if the PI point's digital state set is valid or not.
  • Marco Blokdijk
    Reply
    |
    Aug 19, 2022
    I agree with Dogan. We have the same AF configuration. (One AF server and serveral PIDA servers with different Digital Sets for the same AF Template Attribute). I propose to acknowledge each discrepency for each AF Template Attribute within a PSE session once, or only give a warning without a popup.
  • DmitryK
    Reply
    |
    Aug 19, 2022
    I absolutely agree, it is not very convenient when this message appears.