# Duplicity of properties CRM **URL:** https://community.glideapps.com/t/duplicity-of-properties-crm/69176 **Category:** Ask for Help **Created:** [January 2, 2024, 2:37pm UTC](https://community.glideapps.com/t/duplicity-of-properties-crm/69176 "2024-01-02T14:37:39Z") **Posts on this page:** 1 **Showing post:** 2
### 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: [January 2, 2024, 11:43pm UTC](https://community.glideapps.com/t/duplicity-of-properties-crm/69176/2 "2024-01-02T23:43:22Z")
The usual way for me to do this is to create a custom form, then use a query column to check the destination table for all matches with relevant input columns. If there’s a match, I show an error hint, else I allow them to be added. > [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014): > > 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](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particular… --- _[View the full topic](https://community.glideapps.com/t/duplicity-of-properties-crm/69176)._