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.
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?