# Issue: New relation suggests creating existing entity, which leads to duplication **URL:** \ **Category:** Bugs & Issues\ **Created:** [August 16, 2023, 10:45am UTC](https://community.fibery.io/t/issue-new-relation-suggests-creating-existing-entity-which-leads-to-duplication/4963 "2023-08-16T10:45:01Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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 16, 2023, 12:23pm UTC](https://community.fibery.io/t/issue-new-relation-suggests-creating-existing-entity-which-leads-to-duplication/4963/4 "2023-08-16T12:23:43Z")
> [@YvetteLans](#): > > We have the same end goal as Yuri: make sure user links an existing entity instead of accidentally creating a new one. In that case, it seems that you need Fibery to prevent any attempt to create a new tag/entity with the same name as an existing one, which sounds rather like uniqueness constraints (as part of the more generic ‘validation rules’): > [@Uniqueness constraints for Entities?](https://community.fibery.io/t/uniqueness-constraints-for-entities/2504): > > 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? --- _[View the full topic](https://community.fibery.io/t/issue-new-relation-suggests-creating-existing-entity-which-leads-to-duplication/4963)._