Check for existing value

[mzsadiek]

Hi!

In my app, admins can create new users. However, I want the form to check if an existing user already uses the email address and username. How would I be able to create such a check?

[ThinhDinh]

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 particula…

Make a custom form, then do a relation from your text entry to the list of existing emails/names. If the relation(s) is/are not empty then you show a text telling the user that the email/name already exists.

[mzsadiek]

Thanks for you reply. How would I make a relation if the field being filled is linked to where the email stored? Do I have to make a relation between the textfield and the column it stores the data?

[Darren_Murphy]

That’s correct.
Your input component should be writing the value to a user specific column. You create the relation between that column and the final destination column.

You can make a copy of the app in that linked thread and study it to see how it works.

[mzsadiek]

Thanks! I will try it out and let you know

[mzsadiek]

I’m currently trying to set this up. However, I notice on ‘text entry’ fields I am not able to make them required. On dropdowns (choices) I am able to make them required.

Any possibility to make text entry fields required in a custom form?

[ThinhDinh]

You make them required by not allowing them to submit/move forward if the field in question is empty.

[Darren_Murphy]

@mzsadiek

Any possibility to make text entry fields required in a custom form?

Unfortunately, no. This is one of the drawbacks of using custom forms.
What I usually do is use double asterisks ** to indicate required fields, and then as @ThinhDinh mentions, simply not allow the user to save if all pre-conditions are not met.

Again, if you look at the demo app, there is an if-then-else column that is used for this.

That column only returns true if:

• The supplied name is not a duplicate of an already existing row, and
• The name is not empty

The column is then used in the custom action to determine whether or not the record can be saved.