I start noticing some odd edits from the "constraint violations" games. Maybe we should do some more filtering and suggest different actions.
For constraints that aren't mandatory, an action is likely to save it as an exception, but then maybe non mandatory ones shouldn't flow into the game. Personally, I usually don't bother saving exceptions.
Automatic description failed.
This property is generally expected to contain only a single value.
For this, nothing should really be done. I wonder if any of the "external identifier" properties should have a problem with multiple identifiers being added even if the default is a "single value" constraint.
- remove all cases where the property has "external identifier" datatype
- add option "save exception"
- try to deal with mandatory constraints first