In our system we used validation for uniquness on null (empty) values.
This works before the migration to "Uniqueness validation" on database.
It was exception this dataset:
- 1
- 3
- 5
- empty
- empty
With the database validation this is not possible.
In the release notes of Mendix 6.8 it was even fixed to allow empty values.
Is this a bug in Mendix 7.3 or is there a workaround to avoid this without writing my own Microflow check.