# Checking for duplicates of an entity AFTER adding said entity

**URL:** <https://community.glideapps.com/t/checking-for-duplicates-of-an-entity-after-adding-said-entity/72574>\
**Category:** Ask for Help\
**Created:** [April 14, 2024, 3:24pm UTC](https://community.glideapps.com/t/checking-for-duplicates-of-an-entity-after-adding-said-entity/72574 "2024-04-14T15:24:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [April 14, 2024, 11:21pm UTC](https://community.glideapps.com/t/checking-for-duplicates-of-an-entity-after-adding-said-entity/72574/3 "2024-04-14T23:21:19Z")

</div>

> [@MattGlides](#):
>
> The obvious ideal scenario would be blocking it once a customer adds a vehicle, however I’m assuming due to row owners that would not be possible hence the above.

> [@Conditional logic broken? Duplicates are being allowed when they shouldn't be](https://community.glideapps.com/t/conditional-logic-broken-duplicates-are-being-allowed-when-they-shouldnt-be/72553/3):
>
> The problem here seems to be that you’re using row owners/roles and a user can’t see all of the rows, hence their input can not be matched to all rows. That allows duplicates to happen. Also, I’m not sure why you’re setting the row owner on your Row ID column. Which one is your “role” column in user profiles settings? Nevertheless, I think you must settle for a setup of a “row owners” table for your User Profiles, and a public table for your de-duplicating purpose. Everytime a user f…

Same problem mentioned in the thread above.

---

_[View the full topic](https://community.glideapps.com/t/checking-for-duplicates-of-an-entity-after-adding-said-entity/72574)._