# Uniqueness constraints for Entities? **URL:** \ **Category:** Get Help\ **Created:** [February 6, 2022, 11:13pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504 "2022-02-06T23:13:50Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Mikkling](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@Mikkling](https://community.fibery.io/u/Mikkling)\ **Post date:** [February 6, 2022, 11:13pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/1 "2022-02-06T23:13:50Z")
Is there a way to create uniqueness constraints for an Entity? For instance, I would like a Contacts DB where each contact’s email is unique/primary key, so that an automation that tries to create a new contact with an email that already exists should fail. Or is there some trick i can use to get this effect? ---
**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:** [February 7, 2022, 9:02am UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/2 "2022-02-07T09:02:16Z")
Fibery does not currently have validation rules (e.g. uniqueness, required fields, range-checking etc.) You can implement automations that flag up violations, but there is no enforcement mechanism. ---
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [February 7, 2022, 4:28pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/3 "2022-02-07T16:28:20Z")
Is there a feature request for this? I feel like I saw one but can’t find it now. Having a unique/primary key constraint for new entities is high up on my feature wishlist. ---
**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:** [February 8, 2022, 7:58am UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/4 "2022-02-08T07:58:46Z")
> [@Unique data fields](https://community.fibery.io/t/unique-data-fields/695): > > In our customer management system we assign customers unique ID derived from our accounting. I have created a field for this, and already made a misstep of creating a duplicate customer as I could not find them in my list at first. This is especially handy if creation and data population is done manually. Something like a check-box to check for a field being unique would be nice. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [July 19, 2022, 3:34pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/5 "2022-07-19T15:34:54Z")
You could define a Rule to flag “illegal” entities like so (where ‘Pages’ is the DB, and ‘URL’ is the unique field): ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5c06d60095b2e95a32c9a99247848ae068cda48a.png) It sets the violating entity’s name like so: ```auto If( Pages.filter(URL = [Step 1 Page].URL).Count() > 1, " **DUPLICATE**" + [Step 1 Page].Name, [Step 1 Page].Name ) ``` ---
**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\ **Post date:** [February 19, 2023, 12:38pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/6 "2023-02-19T12:38:06Z")
Has there been any progress on this request? Validation is vitally important to using this software in production. Without it, one can only rely on this as experimental or prototyping software. ---
**Author:** ![cleghornp](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cleghornp/32/9018_2.png) [@cleghornp](https://community.fibery.io/u/cleghornp)\ **Post date:** [March 16, 2024, 3:00pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/7 "2024-03-16T15:00:45Z")
Have there been any changes regarding the validation of fields? Even just forcing users to fill in a field would be better than nothing. Any updates on this? ---
**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:** [April 17, 2024, 12:09pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/8 "2024-04-17T12:09:59Z")
There is nothing to report, I’m afraid. ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [March 22, 2025, 9:31pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/9 "2025-03-22T21:31:11Z")
> [@cleghornp](#): > > Even just forcing users to fill in a field would be better than nothing. Any updates on this? You can always require a value for a given Field now: [February 20, 2025 / 👮 Required Fields, Comments on Whiteboards, Asana integration, some permissions improvements](https://community.fibery.io/t/february-20-2025-required-fields-comments-on-whiteboards-asana-integration-some-permissions-improvements/8290). ---
**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:22pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/10 "2025-05-08T14:22:58Z")
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… ---
**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:** [May 8, 2025, 4:41pm UTC](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504/11 "2025-05-08T16:41:50Z")