Use Dynamic fields to create dropdowns, checkboxes, and radio buttons that are dynamically populated with submitted entries or with categories/taxonomies. Dynamic fields can link entries together and allow users to make selections from data entered in other Formidable forms. Values submitted in Dynamic fields stay linked to the original entry, so that if selections in the original entry are updated, so too are the values in the Dynamic field.
To load options into your Dynamic field from entries submitted in another Formidable form, select Form Entries in the Load Options From dropdown. Nothing is selected in this dropdown by default. Then choose the form to load from, and the field in that form to load the options from.
After you pick which options to load in your Dynamic field, choose how to show them in the Display Type dropdown: Dropdown, Radio Buttons, Checkboxes, or List. Dropdown is the default.
A Dynamic List field displays a value when it has conditional logic that depends on a Dynamic dropdown, radio button, or checkbox field. It doesn't store a value, so this field type isn't available in View or email options.
Dynamic List fields are designed to use conditional logic based on a parent Dynamic field. Set the List field to use the same form that the parent field uses.
For example, a form has a Name field used in a Dynamic dropdown and an Email field used in a Dynamic List field. When a name is selected, its email address shows.
A Lookup or Dynamic field can show its options as images. It does this automatically when the Display Type is Radio Buttons or Checkboxes and the options come from a field that uses images. The source can be a Radio Buttons, Checkboxes, or Product field with image options, or a File Upload field.
These settings then appear in the field options:
Image option label: Shown only when the options come from a File Upload field. Choose another field from the form the options come from to label each image, or keep File name to use the name of the uploaded file.
Image Size: Choose Small, Medium, Large, or Extra Large. Small is the default.
Hide option labels: Check this box to show the images without their text labels.
With a File Upload source, the options show as images only when most of the uploaded files are images.
When you load entries from a form, limit the options to entries created by the user who is filling out the form. To do so, check the Limit options to those created by the current user box in the field options. This box is unchecked by default, and it works for logged-in users only.
The options are sorted in ascending order by default. To change this, choose Ascending (A-Z), Descending (Z-A), or No order set in the Option order dropdown.
You may use Dynamic fields to set up cascading fields. This works well for a country/state/city scenario where the available options are filtered by the value selected in a previous field. Lookup fields also provide this option and there are benefits to using Lookup fields in many situations. Review the differences between Lookups and Dynamic fields to determine which is best for your setup. The biggest differences between the two field types is that Dynamic fields require a separate form for each cascading field and they store the entry ID, where as Lookup fields do not. Follow the steps below to set up a cascading country/state/city setup.
Create a new form titled 'Country'. Add a Text or Dropdown field. Title it 'Country'. Click Update, then use Preview to submit an entry for each country option that you want to have available or import the countries.
Create a new form titled 'State'. Add a Dynamic field and give it the Field Label 'Country'. Its Display Type is Dropdown by default. Set it up to get its options from the Country form > Country field. Add a Text or Dropdown field. Title it 'State'. Click Update, then use Preview to submit an entry for each country and state combination that you want to have available, or import the countries and states.
Create a new form titled 'City'. Add a Dynamic field labeled 'Country' and set it up to get its options from the Country form > Country field. Add a second Dynamic field labeled 'State' and set it up to get its options from the State form > State field. Click Update to save the form. The Anything option in conditional logic appears only after the source Dynamic field is saved. Add conditional logic on the State field so it shows only when Country equals Anything. Add a Text or Dropdown field. Title it 'City'. Click Update, then use Preview to submit an entry for each country, state, and city combination that you want to have available, or import the countries, states, and cities.
Go into the form that your end user will interact with, or create a new form. Add a Dynamic field labeled 'Country' and set it up to get its options from the Country form > Country field. Add a second Dynamic field labeled 'State' and set it up to get its options from the State form > State field. Add a third Dynamic field labeled 'City' and set it up to get its options from the City form > City field. Click Update to save the form.
Add conditional logic on the State field so it shows only when Country equals Anything.
Add conditional logic on the City field. Select All. Then add two conditions: Country equals Anything, and State equals Anything. Click Update to save your changes.
Use a Dynamic field to automatically populate fields based on a selected entry. You need 3 forms: the source form that holds the entries, the 'Select entry' form where the user picks an entry, and the form to autofill. Learn how to populate fields from a selected entry with a Lookup field instead.
Since Formidable Forms 7.0, the fields fill in only for users who can view entries in the admin area (administrators by default) and for the person who submitted the selected entry. Since 7.0.1, that includes a logged-out visitor, in the same browser, for 1 hour after they submit that entry. For anyone else, they stay blank.
If the entries are meant to be public, such as a product catalog, make the source fields public with the example for one field or several fields.
If users only pick entries they submitted themselves, the steps work as written. To list only their own entries, check Limit options to those created by the current user in the Dynamic field. It sits below the Select a Form and Select a Field options. This works for logged-in users only. Guests see the entries submitted by logged-out visitors, and only their own entry fills the fields.
Publish the form that you want to autofill on a page. Copy the URL of this page.
Create a new form called 'Select entry'. This form is where the user will make their entry selection.
Add a Dynamic field. Its Display Type is Dropdown by default.
Set it to 'Load options from: Form Entries, -the form you want to pull values from-, any field'
In the 'Select entry' form, go to Settings → Actions & Notifications.
Under Current Actions, click the Confirmation action to open it.
Select Redirect to URL.
In the Redirect URL box, paste the URL copied in step 1 and add ?pass_entry=[x show=key] to the end. Replace x with the ID of the Dynamic field.
Click Update to save your changes.
Go into the form that you want to autofill and click the field to fill in. Under Advanced:
Turn on Calculate Value.
Select Text.
In the Field Formula box, put [frm-field-value field_id=x entry=pass_entry]. Replace x with the Key or ID of the field in the source form that you want to pull the value from.
Repeat for each field to fill in. Then click Update.
Now when the user submits the 'Select entry' form, it will populate fields with values from the selected entry.
Display values from the entry a visitor selects in a Dynamic field.
Create a new form or go into edit an existing form.
Add a Dynamic field. Its Display Type is Dropdown by default. This will be the field where users will select a value from a submitted entry. Set it up to load options from 'Form Entries'. In the next dropdown that appears, select another form on your site, then select any field in that form.
Set up this field to display as a dropdown, radio button, or checkbox.
Add a second Dynamic field and set its Display Type to List. This will be used to display information from the entry selected in the previous Dynamic field. Set it up to load options from 'Form Entries'. In the next dropdown, select the same form that you selected in the previous Dynamic field's options. Select any field from that form.
Click Update to save the form so the Anything option is available in conditional logic. Then add conditional logic that says 'Show this field if any of the following match: First Dynamic field equals Anything'.
Try it out! Publish your form on a page. When you select an entry from the first Dynamic field, a value from the selected entry will appear in the Dynamic List field.
You can use the following shortcodes to display a variety of information from a Dynamic field in a form's confirmation message, email notification, or View.
Value from linked entry: Display a field value from the linked entry.
[x show="y"]
Replace x with the ID of your Dynamic field and replace y with the ID of any field in the linked form.
Creation date: Display the creation date of the linked entry.
[x show="created-at"]
Replace x with the ID of your Dynamic field
Entry ID: Display the ID of the linked entry.
[x show="id"]
Replace x with the ID of your Dynamic field
User ID information: Show information from the profile of the user who submitted the linked entry. You may use all of User ID shortcode options here.
[x show="user_email"]
Replace x with the ID of your Dynamic field.
Three level entry information: If you have a Dynamic field that pulls from another Dynamic field, you can display information from the form that the second Dynamic field pulls from. You can use any of the above options to display information from the third level form.
[x show="y" show_info="z"]
Replace x with the ID of your Dynamic field, and replace y with the ID of the Dynamic field in the linked form. Replace z with the ID of the field you want to show from the form that the second Dynamic field pulls from. You can also replace z with "created-at", "id", or "user_email".
Option Label: Display the option label instead of the saved value. This differs from the value only when the field that the Dynamic field pulls from is a Dropdown, Radio Buttons, or Checkboxes field with Use separate values turned on.
As of version 5.4, dynamic fields will no longer include data from draft entries. You can use the frm_dynamic_field_include_drafts hook to include both drafts and non draft entries or draft entries only.
This article may contain affiliate links. Once in a while, we earn commissions from those links. But we only recommend products we like, with or without commissions.
In this article
Get More Done In Less Time With Better
WordPress Forms
Upgrade your
workflow with advanced WordPress forms and integrated Views.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
90 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
90 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Easy Digital Downloads is a complete eCommerce solution for WordPress.
Name
Description
Duration
edd_items_in_cart
Stores information about the cart.
Session
edd_session_
Stores information about the current user session.
Session
Formidable Forms is used to manage forms on this website.
Name
Description
Duration
frm_form_
Saves the ID of the form and the time the entry was submitted.
2 hours
These cookies are used for managing login functionality on this website.
Name
Description
Duration
wordpress_logged_in
Used to store logged-in users.
Persistent
wordpress_sec
Used to track the user across multiple sessions.
15 days
wordpress_test_cookie
Used to determine if cookies are enabled.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a web analytics service offered by Google that tracks and reports website traffic.
Used to determine if the user is in a new session/visit.
Session
__utmt
Used to throttle request rate.
10 minutes
__utmv
Used to store visitor-level custom variable data.
2 years
__utmz
Stores the traffic source or campaign that explains how the user reached your site.
6 months
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
fcookie
Used for bot detection.
7 days
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
ccookie
To remember if a user received a captcha challenge.
20 minutes
lissc
Pending
1 year
ABSELB
This is Load Balancer Cookie for affiliate marketing
2 years
spectroscopyId
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
brwsr
This cookie is used to Affiliate Marketing Cookie for LinkedIn
2 years
UserMatchHistory
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
session
lihc_auth_
Used by LinkedIn HelpCenter Live Chat to store language and chat start timestamp. Example names of this cookie include lihc_auth_en, lihc_auth_es, depending on language preference.
Session
lang
Used to remember a user's language setting
session
li_a
Used to authenticate enterprise users on Sales Navigator and Recruiter
30 days
li_gc
Used to store guest consent to the use of cookies for non-essential purposes
2 years
li_ep_auth_context
User to authenticate LinkedIn enterprise customers
30 days
li_rm
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device
1 year
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
lms_ads
This cookie is used to identify LinkedIn Members off LinkedIn for advertising
30 days
trkCode
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
_guid
This cookie is used to identify a LinkedIn Member for advertising through Google Ads
90 days
trkInfo
This cookie is used by LinkedIn to support the functionality of adding a panel invite labeled 'Follow Us'
1 year
BizographicsOptOut
This cookie is used to determine opt-out status for non-members
10 years
li_oatml
Collects information about how visitors use our site.
30 days
IRLD
This cookie is used for Affiliate Marketing Cookie for LinkedIn
2 years
liap
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
90 days
l_page
This cookie is used for measuring conversion metrics on LinkedIn
6 months
pushPermInfo
Used across multiple LinkedIn services to determine cool off for push notification prompts
365 days
pushPermState
Used across multiple LinkedIn services to determine the user's push notification permission preference
30 days
ln_or
Used to determine if Oribi analytics can be carried out on a specific domain
1 day
chp_token
Used to denote whether the user has gone through two factor authentication or solved a Captcha.
Session
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
sdsc
This cookie is used for signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission
Session
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_mc
This cookie is used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side
6 months
PLAY_FLASH
Used by some LinkedIn services to facilitate the display of messages on page transitions . Users include notifying a user when a form is successfully submitted or fails , and to provide other similar notifications.
Session
li_referer
Used to detect bots. Cookie remembers the referring website before redirecting the user to captcha for authorization
15 minutes
f_token
Used to detect bots for anti-scraping
3 minutes
li_apfcdc
Used for triggering the abuse prevention features on member device.
10 hours
li_odapfcc
Used to control the number of abuse prevention features collected from member device.
2 Years
ac_L
Counts the number of times the account center banner, which is displayed to inform users with an incomplete profile how to complete their profile, was closed by a user to determine display logic
180 days
ac_LD
Contains the date when the account center was displayed to a user to determine display logic
180 days
recent_history_status
Used to determine whether a user enabled or disabled the Guest Recent History Setting
10 years
all_u_b
To know if a user has opted in to viewing LinkedIn on an unsupported browser
21 days
uh
Used to set the user preference for the mobile web platform via a user's settings
Session
abiRedirect
Enables import of address book during onboarding flow for users who choose to import their address book
Session
wwepo
Used to ensure that useres who choose to sign up using phone only have that setting and preference respected
90 days
li_cu
Used to map a user to a captcha challenge page
15 minutes
li_ec
Used to store unbound enterprise users' cookie consent
6 months
denial-client-ip
Stores user IP address for anti-scraping and DOS prevention
5 seconds
li_gpc
Used to remember a user's preferences on LinkedIn's Global Privacy Control
1 hour
denial-reason-code
Used for anti-scraping and DOS prevention
5 seconds
li_gp
Stores privacy preferences for guests to LinkedIn
1 year
rtc
Used as part of anti-abuse processes on LinkedIn
120 seconds
redirectFromM2MInviteSent
Used to notify and provide the appropriate profile display logic when the user sends an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
queryString
This cookie is used to persist marketing tracking parameters
15 days
cookie.policy.banner.eu
Used to display cookie banner in LinkedIn Lite
365 days
cookie.policy.banner.nl
Used to display cookie banner in LinkedIn Lite on the Netherlands site.
365 days
appName
Used to identify the source as the LinkedIn Lite app to send the right service worker to the app
Session
appLang
Used to set the right language on the LinkedIn Lite app
Session
lls-integration
Validates whitelisted partners for content integrations
30 days
feed-sort
Used to remember a member's preference how the feed should be sorted
1 day
integration_type
Used to determine which integration traffic is coming from to render the profile namecard experience
30 days
li_theme_set
Remembers which users have updated their display / theme preferences
6 months
PLAY_LANG
Used by some LinkedIn services to remember a user's language preference
Session
lms_analytics
Used to identify LinkedIn Members off LinkedIn for analytics
30 days
PLAY_SESSION
Used by some LinkedIn services to store session information
Session
li_fat_id
Member indirect identifier for Members for conversion tracking, retargeting, analytics
30 days
redirectFromM2MInviteAccept
Determines the appropriate profile display logic when a user accepts an invitation to connect on LinkedIn from a LinkedIn member via email.
Session
li_giant
Indirect indentifier for groups of LinkedIn Members used for conversion tracking
7 days
sharebox-suggestion
Displays a banner that provides help text to first time users of the Elevate share box
Session
li_cc
Used to ensure a user's phone number is inputted in China
1 week
lss_bundle_viewer
Stores consent when a user agrees to view a Smartlinks link
1 month
interstitial_page_reg_oauth_url
Stores the referring page to ensure the Authentication screen displays correctly
1 day
df_ts
Device fingerprinting sampling for performance optimization
1 day
lil-lang
Stores user's selected language setting for LinkedIn Learning
Session
li_alerts
Used to track impressions of LinkedIn alerts, such as the Cookie Banner and to implement cool off periods for display of alerts
1 year
li_theme
Remembers a user's display preference/theme setting
6 months
li_feed_xray
Used to show new items in developer option 'Feed X-ray'
Session
VID
ID associated with a visitor to a LinkedIn microsite which is used to determine conversions for lead gen purposes
1 year
recent_history
Used to remember URLs visited by the guest to show the pages back where they left off
90 days
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Name
Description
Duration
affwp_campaign
Stores the affiliate campaign name for tracking purposes.
30 days
affwp_ref
Stores the referring affiliate ID for commission attribution.
30 days
affwp_ref_visit_id
Stores the visit ID linked to the referring affiliate.
30 days
LinkedIn Insight is a web analytics service that tracks and reports website traffic.