Create forms with query to read and create a email

[jaquelinedealmeida]

1- In the first screen I need to verify if the email is in the database already. I am using a query to create a new register and the query adds only the field with a binding relation email.
If the e-mail doesn't have in the database, it continues the navigation to the next screen.
If is in the database, stop the creation and send a warning.
I put the actions in the button.

But when I test with an email registered already, I can navigate to the next screen.

How I can better this?

[mikesealey]

Hi @jaquelinedealmeida

There are two ways to go about this. Both look the same to the end user, but under the hood there's a few differences. To explore this, I created an app with a form-field that requests an email from the user, and on click of the button the app will check existing user emails. Using a Navigate To action and some JavaScript to return the path of the page depending on the response of the check

Premium Users

• If you're a premium user of Budibase, navigate to the Automation tab and create an App action.
• Add a field to the app action called email, set to text.
• Add a Query Rows step to the automation, select the table to query, set the limit to 1
• Define the filters: The column you wish to check (most likely email, in your case) EQUALS BINDING {{ trigger.fields.email }} (Your own variable names may differ slightly, use the bindings menu to assist).
• Add another step to your automation - this time Collect Data. Set it to collect the Step 1 Outputs rows (again, bindings menu will help).
• In the Design screen, at the point where you want to check if the email exists (ie a submit-button) you can then use actions to trigger that automation, and a Navigate To action. (Again, your variables may differ, but...) my Navigate To action looks like this:

if ($("Action 1.Automation Result").value.length === 1) {
  return "/exists"
} else {
  return "/doesntexist"
}

The Automation Result is an object containing an array named Value - if there is an email address already in the table, it will appear here, giving the object a length of one, and therefor navigating to (in my case) /exists.

Free Users

• In the Data tab, create a new data source, and select REST API, then name it something useful like "Check Email Exists"

• Click Create New Query, select POST, and set the URL to location of your table - I'm using the Budibase sample data, so mine is https://budibase.app/api/public/v1/tables/ta_bb_employee/rows/search

• Add a binding "email" (use the default value here for testing/debugging, if you need to)

• Under "Headers" you'll need your API key and your App ID - you can find out where to get them both from in the documentation here. You should add them under the keys "x-budibase-api-key" and "x-budibase-app-id" respectively.
  

• Under "Body" add the following as raw(JSON):

{
  "query": {
		"equal": {
      "Email": "{{ Binding.email }}"
    }
  }
}

Where Email (capital E) is the column in the table you're querying, and {{ Binding.email }} is from the Bindings header.

• In the Design screen, at the point where you want to check if the email exists (ie a submit-button) you can then use actions to execute the query - you'll need to set your datasource and query to the REST API you've just created, and you should use the Bindings to capture the email from the form.
• You should then use an Update State action to store the response of the query, followed by a Navigate To action which uses some JavaScript to decide where to go based on the value stored in state.

if ($("Action 1.Query result").data.length === 1) {
  return "/exists"
} else {
  return "/doesntexist"
}

As always, your variables, bindings, and keys, will be unique to your project, so this answer should be used as a template rather than a solution. There's always more that can be said, so the Budibase Discord Server is a useful place to be, and the Budibase Documentation is worth bookmarking to have open in a tab in the background for more guidance.

I hope this helps!

[jaquelinedealmeida]

Thank you. I am testing the aplication!

[mikesealey]

Hi @jaquelinedealmeida I'm sorry you're still having trouble. I've attached the export file of the app I used to explore this. I just used the sample data, and for ease I've included the table of emails on the home screen so you can copy/paste them from the table to the field for testing.

13622-export-1715330961240.tar.gz

You can read about how to import apps in the documentation here.

[jaquelinedealmeida]

Thank you!! It's working!
I change the condition!

if ($("Action 1.Query result").data.length === 0) {
  return "/new_page
} else {
  return "/same_page"
}

[jaquelinedealmeida]

Hi @mikesealey . I tested it again, but it's just going into the else.
Even if I change the order of the condition, the redirection of the screen to the unregistered email is always the same, as if it were in the database. I'm using a Rest API from nocodb and wondering if there could be any relation for that.

I still haven't been able to identify the error.

[mikesealey]

For debugging purposes, temporarily remove or disable the "Navigate To" action and add in a "Show Notification" which contains the $("Action1.Query result").

In it's current setup we're looking for an empty array, but the if-statement will take you down the else-path if you get literally anything else, so it could simply be that we've made an incorrect assumption earlier that is causing unexpected behaviour.

[jaquelinedealmeida]

I fixed with ($("Action 1.Query result").data[0].list.length === 0)

[mikesealey]

Perfect, I'm glad you got sorted!

[jaquelinedealmeida]

Thanks!