In 16.0.2 users are getting an error that benefit Plan Description (Detail), which is a string field, that has to be unique. Is this a new constraint recently introduced?
I have tested this on 16.0.1 and 15.9.3 instances and whilst the attribute is defined as unique, this is not enforced by the UI in Classic. Is this a defect or is this now behaving as expected?
There is a description field in both objects Benefit Plan and Benefit Plan Details
On the Benefit Plan is not set as unique and the value can be across several benefit plans. This is the case of the tests on earlier releases
The one that is unique is the one on the Benefit Plan Details object.
The rows inside the benefit plan itself can not have the same description. It must be unique and it has always been that way.
If the description field is updated with the value of another instance, then you get the error:
REVMGR-01102:The value for Detail has to be unique