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

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.

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?

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.  

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.

Each attribute is pointing to a different tag with a defined digital state set.

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.

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.

I absolutely agree, it is not very convenient when this message appears.