Chained Selects 1.8.1 – Gravity Forms Add-On

Chained Selects – Gravity Forms Add-On is used when you need dependent select fields: the user picks option A, and option B’s choices update based on that selection (and sometimes option C updates based on B).

Common real uses:

• Country → State/Province → City
• Category → Product line → Model
• Department → Team → Role
• Make → Model → Trim (quote forms)
• Any form where showing all choices at once would be messy or error-prone

How it works (practically) inside Gravity Forms

• You create a Chained Selects field and define a data set (the allowed combinations).
• On the front end, JavaScript listens for changes to the parent select(s) and repopulates child choices.
• The submitted value is validated against the allowed combinations so users can’t submit an invalid pair by tampering with HTML.

Where configuration usually lives:

• Form editor → add the Chained Selects field → configure the chain structure + choices/data
• If it supports importing: many sites build the chain data in CSV and import it (faster than manual entry)

Where it usually breaks + quickest fixes

Child dropdown doesn’t update (stays empty) Most common cause: JavaScript conflicts or script optimization.

• Fix: temporarily disable JS minify/defer/delay and retest.
• If that fixes it: exclude Gravity Forms scripts and the chained-selects script from optimization. Also avoid delaying jquery-core.

Works on desktop, fails on cached/optimized pages Root cause: caching plugins altering inline scripts or delaying event bindings.

• Fix: exclude the form page from “Delay JS”, or exclude Gravity Forms inline scripts from minification. Purge cache after changes.

Conditional Logic behaves oddly Example: a chained field is hidden/shown and doesn’t repopulate correctly.

• Fix: ensure the field is not being reset by conditional logic rules; retest with conditional logic disabled to isolate.
• If it’s on a multi-page form: test on a single-page version—multi-step transitions can affect when the chain initializes.

Dynamic Population / prefill doesn’t set the chain If you’re preselecting values via query strings or hooks, the plugin may need the parent value set first, then trigger change events.

• Fix approach: confirm the parent select is populated before the child attempts to load; in custom code, trigger a change event after setting the value.

Performance notes (what matters on large chains)

• Very large datasets (thousands of combinations) can make the field heavy. If users complain about lag:
  • reduce chain depth where possible,
  • split into separate form paths (conditional sections),
  • keep choices tight (don’t dump a whole catalog into one chain).

Updates / compatibility checklist (what I verify)

Before updating WordPress or Gravity Forms on a production site using chained selects:

• confirm plugin version supports your Gravity Forms major version,
• test one form submission end-to-end (especially with AJAX-enabled forms),
• if Woo/CRM integrations depend on the selected values, confirm the stored value format didn’t change.

You can find detailed instructions on how to update a theme or plugin on this page.

Practical FAQ (things devs actually ask)