Collections expanders are released today as experimental @DiegoKamp you may try them out
There is no built-in way to guarantee uniqueness on creation, but there is a workaround: You can set up a new relation with itself and set it to auto-link on the unique field. Call it “Duplicates”. Then you can see all duplicates in the entity view and/or set up automations/formulas/add 
to the name, etc. based on that collection for manual check-up.
You might want to check out the deduplication template we have, for inspiration on how you can address the issues of non-uniqueness.
Guaranteeing uniqueness on creation is pretty hard to implement with Fibery’s current architecture.
Thank you very much! Done. It’s an ingenious solution. Of course, if you have more than one field it can become heavy to implement and manage. Have you already tried creating multifield uniqueness constraints, as you can easily do in Microsoft Access through indexes? It would be a great achievement.
Good evening.
I succeeded, just insert all the fields you want to check in the report:
and it works, it intercepts duplicates of the two fields. Situations like this
Name Cognome Controllo
nome1 cognome1 Attenzione record duplicato
nome1 cognome1 Attenzione record duplicato
nome1 cognome2 Ok
, the “controllo” field contains a very simple formula with an “if”
If([Prova duplicatis].Count() > 1, “Attenzione record duplicato”, “OK”)
Very good so for simple situations it is a workable solution.
Certainly when you have a database with many fields and controls of this type, the solution is difficult to apply, making the database structure very heavy.
A solution at the structure level would be desirable, using indexes as happens in Access, where even very complex constraints can be created.
Thanks again.
Unique values for fields released today as experimental
1 Like