Best Practise: Unique Constraints on an Entity with multiple attributes
How does one setup a Unique Constraint on an entity using multiple attributes? Is this configurable in the data modeler, or should I be using a 'Before Commit' microflow to check the 'Uniqueness' of the Entity to be committed against what exists in the database?
Rail Da Ribeira
If the uniqueness is based on several attributes e.g. person first name, last name and organisation should be unique in combination this can only be checked with a before commit MF. The modeler only allows to check via validations if a specific attribute is unique not the combination of attributes.