Duplicity of properties CRM

[Fabio_Carneiro]

Hello everyone, I’m going to ask for help with something that is very complex for me and I’m not able to make it work as requested, I’m going to explain a little how it works and the best I could do.

I’m creating a CRM for property sales, and it’s important that before registering a new property, the system can inform me if it already exists. It doesn’t work because it seems that as I enter the information in the fields, it will be inserted in the table, so when the form is sent the property will always exist and duplicity will be accused. This is a serious error and I need this to work, the solution I created was to use a “hint” element that, based on a Javascript column, shows a warning that the property has already been registered, the Javascript column works in a simple way, it receives a number, and analyzes whether this number is in a joined list, these numbers are the concatenation of 3 values:

property number
zip code number
and property reference number

For better understanding, a house in any neighborhood will have the house number and the zip code. If it is an apartment, it will have the condominium number, zip code and apartment number, based on this we will have a number such as:

13033876123654

considering it is an apartment, for example. Considering this number, the Javascript analyst if it already exists in a joined list to find out if this record has already been made, the Row ID column has another purpose, here it is duplication of the property and not the record in the table, especially because in two rows in the table I can register the same property with the same data, and this cannot happen.

the perfect situation would be for the system to inform you that the property already exists and not lose the data already entered in the registration form, but if it can’t, ok, another thing, each action of the brokers is recorded in a control column, we need this to analyze events and ensure data security, etc. So I need to analyze this duplicity, before sending it to the tables so that an action is not registered without it actually occurring, this would trigger, several property registrations in failed attempts where the property was not registered, I tried to explain as much as possible of details.

[ThinhDinh]

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?

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…

[Fabio_Carneiro]

wonder! Thanks for the answer, by superficially analyzing the example app, I was able to analyze that a “hint” component is responsible for the duplication warning, would this be the only way to apply this functionality? One of the three images I posted here shows this working, which is the solution created by me so far

[ThinhDinh]

Yeah, I think that’s the correct interpretation. A hint when there’s a match (to show an error), else you allow to “Save”.

[Fabio_Carneiro]

In the case of using a personalized form, it is because you can control the “save” button so that it is only clickable if the duplication rule is indicating it as a new record, correct?

[Darren_Murphy]

Yes, that’s correct.

[Fabio_Carneiro]

For now, I will keep the common form because it is triggered at several different times, I will ask the CEO about the possibility of implementing a customizable form. Would this customizable form then be a page that acts as a form and is used as a targeting target when we need to register a new record?

[Darren_Murphy]

I’m not sure I totally understand your question, but… a Custom Form can be re-useable. The way to make it like that is as follows:

• Use a separate single row helper table to drive the form
• Build the form on a Details screen that uses that table as the source
• In your User Profiles table, add a Single Value->First->Whole row column that targets the helper table
• Any time you need to use the form, open it via a Show Details screen action via that Single Value column

When you set it up as above, the form can be opened from anywhere in your App.

[Fabio_Carneiro]

This auxiliary table would be to receive the form data and this data would be compared with the table where the definitive record will be located, and where it will be used to analyze whether there is already data equal to that in the auxiliary table?

[Darren_Murphy]

You would do that in the helper table.
You need to build whatever relations and or queries that you would need to compare the entered data to the already stored data.

[Fabio_Carneiro]

I’m happy with that, I thought about this data flow before creating this duplication system that is working, an expert recommending something I thought makes me believe that I’m thinking correctly, thank you for everything and for the shared knowledge!