Checking for duplicates of an entity AFTER adding said entity

[MattGlides]

We currently have row owners in place so one customer cannot accidentally see another customers vehicles and for added security.

The issue is we do not want two separate customers to have the same license number as this causes errors in the system when they go to fill-up.

How can I do a check for duplicate license numbers at fill-up (currently a customer drives in, the attendant enters the license number, and it does a relation to a vehicle in our data. I want it to block if theres a dupe). On top of that, admins are able to see all vehicles via a second row owner. How can I do a query that will show them the duplicates?

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.

[nathanaelb]

Maybe this will help:

How do I create a custom form?

I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using User Specific Columns and Relations Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particular…

[ThinhDinh]

@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

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. [image] 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.

[Darren_Murphy]

Give the attendants a common role, and make that role an owner in the vehicles table.