# Fibery for knowledge management, what I desire **URL:** \ **Category:** Ideas & Features\ **Created:** [August 11, 2024, 2:34pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497 "2024-08-11T14:34:41Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 14, 2024, 12:27pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/27 "2024-08-14T12:27:07Z")
Collections expanders are released today as experimental @DiegoKamp you may try them out > [@August 14, 2024 / robot Manage automation Rules as a Creator, New sidebar design, Expand cards to show nested collections](https://community.fibery.io/t/august-14-2024-manage-automation-rules-as-a-creator-new-sidebar-design-expand-cards-to-show-nested-collections/6504): > > Tomorrow is a holiday in Poland and Cyprus, so we are releasing today. This release has at least one long-awaited feature, sprinkled by some less expected things. Enjoy! [image] robot Manage automation Rules as a Creator (special for Shlomi, Rob, and 40 more people) No more 12 Admins in a workspace, no more “could you please set up this Rule for me”. Now everyone with Creator access to a Space can configure no-code automation Rules and Buttons. Since you can traverse relations beyond the c… ---
**Author:** ![lars](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lars/32/7322_2.png) [@lars](https://community.fibery.io/u/lars)\ **Post date:** [August 14, 2024, 2:42pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/28 "2024-08-14T14:42:29Z")
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. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 14, 2024, 2:58pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/29 "2024-08-14T14:58:53Z")
You might want to check out the [deduplication template](https://fibery.io/templates/deduplication) 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. ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [August 14, 2024, 7:42pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/30 "2024-08-14T19:42:17Z")
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. ---
**Author:** ![DiegoKamp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/diegokamp/32/4588_2.png) [@DiegoKamp](https://community.fibery.io/u/DiegoKamp)\ **Post date:** [August 14, 2024, 8:04pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/31 "2024-08-14T20:04:32Z")
I succeeded, just insert all the fields you want to check in the report: ![image.png](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2d8ca9ffc112214e7b0903a0c9ff167272587c0b.png) 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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 8, 2025, 2:26pm UTC](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497/32 "2025-05-08T14:26:03Z")
> [@DiegoKamp](#): > > The lack of the uniqueness constraint was one of the first limitations I pointed out. It also amazed me that not only Fibery does not provide this feature, but neither do all the other competitors. Unique values for fields released today as experimental > [@May 8, 2025 / New "this week/..." filters, Unique field values (experimental)](https://community.fibery.io/t/may-8-2025-new-this-week-filters-unique-field-values-experimental/8751): > > We are back from the Spring holidays season and can finally release something (many large things are in progress still, including permissions things, Gantt View and AI Smart Agent). New filters: is within past/current/next week/month/quarter/year Now you can filter views by past/current/next week/month/quarter/year. It will make your life a little bit easier, since you will no longer have to update manual filters every week/month/quarter/year. Allow only unique values in a Field (exp… [Previous page](https://community.fibery.io/t/fibery-for-knowledge-management-what-i-desire/6497.md?page=1)