Product Finder
In this Lookup field field example, assume you want to create a simple product finder that staff can use to look up product codes.
You can achieve this by using a series of drop-down list lookups linked to a separate source form containing the product information.
By enabling the cascade feature, the selection in the first lookup field determines the list of options in the following lookup field.
The Name field is hidden with conditional logic until the last lookup returns a matching field value from the source form.
The following is an overview of the form fields and settings required to create this lookup.
The source form Firstly, you create a datasource to provide the product information for the lookups in our Product Finder form.
You create a basic source form called 'Product Database' with the following fields:
-
Category (Short answer)
-
Subcategory (Short answer)
-
Model (Short answer) To prevent the entry of duplicate model numbers when this information is collected, we enabled the Do not allow previously entered value option in this field’s advanced options.
-
Name (Short answer)
Collect data
You create a simple database of our products by submitting the required details for all items.
| For large volumes of data, please contact Advanced Forms Support and request bulk uploads to be enabled. |
You can confirm or edit the submitted information through the Form Responses List.
The master form
After completing the source form, you create a separate form called Product Finder that will be used to perform the lookups.
This form contains the following fields:
-
Category (Dropdown list)
-
Subcategory (Dropdown list)
-
Model (Dropdown list)
-
Name (Short answer)
Use the same field names as your source form to ensure successful field matching when using lookups to autopopulate fields in your master form.
Lookup field - Category
| Field/Option | Setting |
|---|---|
Lookup Type |
User selects from a drop-down list of possible values. |
Source Form |
Product Database |
Source Field |
Category |
Automatically populate other fields after lookup |
Disabled |
Cascade filter answers based on another lookup field |
Disabled |
Hide lookup result message |
Disabled |
Lookup field - Subcategory
| Field/Option | Setting |
|---|---|
Lookup Type |
User selects from a drop-down list of possible values. |
Source Form |
Product Database |
Source Field |
Subcategory |
Automatically populate other fields after lookup |
Disabled |
Cascade filter answers based on another lookup field |
Enabled, depends on 'Category'. This will filter the list of subcategories based on the category selected in the previous lookup field. |
Hide lookup result message |
Disabled |
Lookup Field - Model
| Field/Option | Setting |
|---|---|
Lookup Type |
User selects from a drop-down list of possible values. |
Source Form |
Product Database |
Source Field |
Model |
Automatically populate other fields after lookup |
Enabled When form users select a model, the system will autopopulate the Name field with the corresponding product name for that model contained in the source form. |
Cascade filter answers based on another lookup field |
Enabled, depends on 'Subcategory'. This will filter the list of models based on the subcategory selected in the previous lookup field. |
Hide lookup result message |
Enabled. You do not want a result message to appear after the lookup is performed and auto-populates the Name field. |
Short Answer Field - Name
Each product model correlates with a specific product name in the source form database.
For example, a 90-liter chest freezer model is named FZCH90.
Instead of performing an unnecessary lookup, we simply used a Short answer called Name, and let the Model lookup field’s response (selected value) automatically populate the Name field.
Set a conditional logic rule to hide this field until a model is selected.
When a form user selects a model, the Name field appears with the corresponding value pre-filled.