Gravity Wiz

Magically enhanced tutorials, snippets and plugins for Gravity Forms!

Require an Existing Value for Submission with Gravity Forms

Ensure that a value entered in Form B has been previously submitted (or generated) on Form A. This is useful if you're generating a reference number of some sort on Form A and would like the user to enter it on Form B.

Last updated | Written by 81 Comments

  • June 22, 2022: Improved support for validating field map via AJAX.

  • June 2, 2022: Changed behavior to validate blank target values by default. This can be changed using the validate_blank_values parameter.

  • July 16, 2021: Fixed a compatibility issue with GP Populate Anything.

  • March 11, 2020: Fixed issue where target and source field were mixed up. How did this bug exist for so long!?

  • October 5, 2019: Fixed issue where AJAX validation was not working correctly when specifying fields via the field_map property.

  • February 7, 2017: Fixed issue where submitting the form before AJAX validation had completed resulted in a failure to capture the target field's value.

  • February 6, 2017: Fixed two issues with validation; validation did not work correctly on submission; AJAX validation was not validating against the correct source field ID.

  • February 5, 2017: Added support for AJAX validation; value is validated as soon as the user exits the input.

  • August 29, 2016: Updated article with documentation for "field_map" parameter.

  • May 14, 2015: Updated does_value_exist() method to only query active entries.

Show All Updates
View DemoView CodeDownload Code

Let’s say a reference number is generated on Form A (using something like GP Unique ID) for the user’s order (represented by a Gravity Form entry). The reference number is emailed to the user.

On Form B, the user is able to contact you about their order by entering the reference number. If they fail to enter a valid reference number, a validation error is returned and they are unable to submit the form.

validate-that-a-value-exists-for-a-gravity-formThe form will generate this error unless a valid reference number is entered.
Looking for an simple way to generate a reference number for your Gravity Form submissions? GP Unique ID for Gravity Forms can help.
Check out this step-by-step tutorial on how to use GP Unique ID to generate a reference number for your Gravity Form submissions and use this snippet to validate those reference numbers on subsequent submissions.

How to Generate and Validate a Reference Number for Gravity Forms with GP Unique ID

Getting Started

  1. Check requirements
  2. Install the snippet
    • Copy and paste the entire snippet into your theme’s functions.php file.

  3. Configure the snippet

    • Once you have installed the snippet, look at the bottom of the snippet for this block of code:

      new GW_Value_Exists_Validation( array(
	'target_form_id'  => 123,
	'target_field_id' => 1,
	'source_form_id'  => 124,
	'source_field_id' => 1,
	'validation_message' => 'Hey! This isn\'t a valid reference number.'
) );

    • The target form ID and field ID represent the form and field that should be validated and show the validation error when validation fails.
    • The source form ID and field ID represent the form and field that store the existing value that the value submitted in the target form and field should be checked against.
    • The validation message can be updated to any message you would like to indicate that the entered value did not match any existing values in the source form and field.

Parameters

  • target_form_id (integer) (required)

    This is the Form ID for the field that you will checking if a value already exists (Form B in the example above). There is no default value.

  • target_field_id (integer) (required)

    This is the Field ID for the field that you will checking if a value already exists (Form B in the example above). There is no default value.

  • source_form_id (integer) (required)

    This is the Form ID for the field that generated the reference number (Form A in the example above). There is no default value.

  • source_field_id (integer) (required)

    This is the Field ID for the field that generated the reference number (Form A in the example above). There is no default value.

  • validation_message (string) (optional)

    This is the error message that will be displayed if the value being tested does not already exist. Defaults to "Hey! This isn't a valid reference number."

  • field_map (array) (optional)

    An array of target and source field IDs; allows for creating multiple requirements that must match the same entry. Format should be:

    array(
        // TARGET_FIELD_ID1 => SOURCE_FIELD_ID1,
        2 => 3,
        5 => 11
    );

  • disable_ajax_validation (bool) (optional)

    Optionally disable AJAX validation. AJAX validation is enabled by default and will add a checkmark or an x-mark depending on whether the value exists.

  • validate_blank_values (bool) (optional)

    Set to false if you wish to disable validating blank target field values.

Validate phone numbers on your forms in real time with Gravity Forms Advanced Phone Field! This perk also detects country codes automatically, formats numbers accordingly, and provides animated drop down selects (complete with flags 🇺🇸).

Any questions?

This snippet is more of a building block rather than a final solution. Let us know how you’re using it and any questions you have about building on top of it to accomplish a more involved solution.

For an example of how this can be combined with other plugins to create a more robust solution, check out the How to Generate and Validate a Reference Number for Gravity Forms with GP Unique ID tutorial.

We hope you find this snippet useful! If you do, show us some love by sharing this article on the social media platform of your choice. Let’s keep the Gravity Wiz pumping out awesome snippets.

Did this resource help you do something awesome with Gravity Forms? Then you'll absolutely love Gravity Perks; a suite of 43+ essential add-ons for Gravity Forms with support you can count on.

Comments

    • Dario Space says

      Hi Brian,

      You will need to add two instances of the configuration to validate two fields. In the snippet you’ve sent, there’s only one. If you have an active Gravity Perks license, can you get in touch with us via our support form.

      Best,

  3. Ozz says

    Hi David,

    I would love this exact snippet doing the opposite. If the value entered already exists within all the forms entries, users should get an error message and can’t submit the form until a unique value is entered. Is there a version to do the exact reverse by changing the true and false states? I have tried the limit submissions but it doesn’t pick up previous entry fields?

    Reply

    • Dario Space says

      Hi Ozz,

      We’ve already followed up on this via email, but I wanted to post this in the comment thread so other customers could see it.

      Limit Submissions Perk should work when using a Form Field value as a limit.

      Best,

  4. Brandon says

    I have a theoretical question. I’m using Gravity Forms for support tickets, but only certain websites are eligible for support. I want to validate their website. Could I create a user registration form (Form A) where they put in their website address and then use that form as a source of validation that their website is covered on Form B? Also, lets say their support coverage ends on that website, would I need to delete the entry in Form A, or could I use the field_map parameter to look at a field in Form A that shows whether that website’s support is active?

    Reply

    • Samuel Bassah says

      Hi Brandon,

      Your solution looks like a good one and it should work perfectly for what you want to achieve. Form A, which is the user registration form will contain the entries with website addresses that Form B will use to check if a User’s website is eligible for support. Currently, you’ll have to delete an entry if a user’s support coverage ends. However, if you’ll want to keep those entries when the support coverage ends, a workaround will be to manually append a text to the website URL on the Entry page, so that when a user enters it in Form B, there wouldn’t be a match.

      Best,

  5. Marcel says

    Hi,

    How would I go about using the snippet for multiple forms. Example: I want to validate field id 1 in form 1 against field id 2 in form 2, but then I also want to validate field id 1 in from 3 with field id 2 in form 4. So basically more than 1 source id and target id. I tried to copy the code twice in functions.php and renaming the class and some of the functions, but looks like it calls the init of the first.

    Thanks, Marcel

    Reply

  6. Marcel says

    Hi,

    this does not seem to work across forms,but only when source and target form ids are the same…. is there a bug?

    Thanks, Marcel

    Reply

  7. churmi says

    How would I add a date condition to the validation? So not only does the code but it validates the date as well. For example it validates the code and also the date_created against the current date. Where the current date is not more than 3 days from the date_created.

    Anyone have any ideas?

    Reply

    • Samuel Bassah says

      Hi Churmi,

      This may be possible with some changes to the snippet, but unfortunately, we are unable to assist with snippet customizations at the moment.

      Best,

  9. Jerry Lin says

    Will this work to cross validate between forms? Example: Check if name and dob exists from form a to form b.

    Thanks

    Reply

  11. HAMMAL MANSOOR says

    Looking for help to use this snippet Hey can you we validate to target ids in the form A with one source id in Form B ? if yes what changes need to be done in the code above?

    Reply

    • HAMMAL MANSOOR says

      @David. I mean I want to validate the code in two different places in form A and both the code as the same source Form B how can I do that.

  12. Stephanie Ferreira says

    I can modify for the user only have access to the form if the payment of woocommerce is marked “Completed”?

    Reply

  13. Lakewood Web says

    Hi, Thanks for your previous reply. Is it possible to have multiple instances of this snippet e.g. for two separate forms? Can you explain how? Thanks!

    Reply

  14. Lakewood Web says

    1) Same question as Adesola 2) Can I validate against the “Entry ID” field? how do I get the ID of that field? Thanks!

    Reply

  16. Michael says

    Hi David, I found your script and I wonder if it can be a base for a solution from my task. I tried to customize the script, but it does not work. Is there a chance to help me?

    May task: I have 3 relevant fields: 1: username 2: projectnumber 3: shared username

    If a user creates an entry to be searched if the same number already exists in another entry. If the number already exists the username of the first user should be entered in field 3. The reason is the following: it is allowed to use identical numbers multiple times. but the users should be shown, which user has already used these identical numbers.

    Kind Regards Michael

    Reply

  17. Ahmed says

    Hi, Thank you for your great effort. I tried to use it and it did work however when i try to use the field_map, it doesn’t stick to the pointed source_field_id only but it also accepts any entries from other fields ids if the entered value matches. My example below: the field id 12 – form 18 should only validated through field id 5 – form id 17 and the field id 6 – form 18 should only validated through field id 3 – form id 17 but what happens is that if the entered value in field 12 matches an entry value at field id 3 it marks it as valid and continue and same for field id 6 and source field id 5.

    Please help.

    Thanks in advance

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

By commenting, I understand that I may receive emails related to Gravity Wiz and can unsubscribe at any time.