There are several ways to automatically populate fields. You can fill fields with values from the current user's profile. You can also fill them with values submitted earlier by the current user, from the same IP address, or in a specific entry.
If your users go directly from Form A to Form B, you can pass values from Form A to Form B with the entry key. You can also populate fields with Dynamic fields.
When users go directly from Form A to Form B, Form A can send its entry key to Form B in the page address. Form B then uses that key to fill its fields with the values from Form A.
Since Formidable Forms 7.0, Form B fills in only for administrators and for the logged-in user who submitted the Form A entry. For logged-out visitors, including a guest who just submitted Form A, and for other users, the fields stay blank.
If your users are logged in, the steps below work as written. Learn how to populate fields for the current user, the simplest option for logged-in users.
If your users aren't logged in, add the PHP code example to show guests their own entry on the next form to your site, and replace its form ID with the ID of Form A. Each guest then sees only the entry they just submitted.
Don't make the Form A fields public with the frm_field_value_requires_ownership filter when Form A collects private information. Anyone can change the entry key in the page address and see another person's entry.
Go into Form A and click on Settings → Actions & Notifications.
Under Current Actions, click the Confirmation action to open it. Then select the Redirect to URL button.
In the Redirect URL box, insert the URL of the page that contains Form B. Then add a parameter that includes the entry key from Form A.
Leave [key] as it is. This shortcode gets the entry key.
Go into Form B and click the field to fill in. Under Advanced, turn on Calculate Value and select Text. Then put the [frm-field-value field_id=x entry=pass_entry] shortcode in the Field Formula box. Replace x with the ID or key of a field from Form A. This shortcode pulls the value from that field in the Form A entry.
To populate a File Upload field, put the [frm-field-value field_id=x entry=pass_entry show=id sep=","] shortcode in its Default Value box instead. Replace x with the ID or key of the File Upload field from Form A.
Now, when a user submits Form A, they're taken to Form B. The entry key from Form A is passed in the URL. The frm-field-value shortcode uses it to fetch the values from the Form A fields.
From Idea to Reality in Minutes. Build Powerful Forms, Dashboards, Apps and More.
Formidable Forms makes advanced site building simple. Launch forms, directories, dashboards, and custom WordPress apps faster than ever before.
To populate fields with values submitted by the current logged-in user, insert the [frm-field-value field_id=x user_id=current] shortcode into the Default Value box in the field options. Replace x with the ID of the field that you want to get the value from.
If the current user has submitted several entries in that form, this shortcode gets the value from the user's most recent entry. It's the simplest option for logged-in users. Logged-out visitors see a blank field.
To populate fields based on an entry the user selects, use a Dynamic field in a separate form.
Since Formidable Forms 7.0, the fields fill in only for administrators and for the logged-in user who submitted the selected entry. For anyone else, including logged-out visitors, 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 when they're logged in. To list only their own entries in the Dynamic field, check Limit options to those created by the current user under Select a Form. This works for logged-in users only.
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 makes their entry selection.
Add a Dynamic field with Dropdown as the display type.
Set it to load options from Form Entries. In the next dropdown, select the form that you want to pull values from. Then select any field from that form.
Go into the Select entry form and click on Settings → Actions & Notifications.
Under Current Actions, click the Confirmation action to open it. Then select the Redirect to URL button.
In the Redirect URL box, insert the URL copied in step 1.
Add ?pass_entry=[x show=key] to the end of the URL.
Replace x with the ID of the Dynamic field.
Go into the form that you want to autofill and click the field to fill in. Under Advanced, turn on Calculate Value and select Text. Then put the [frm-field-value field_id=x entry=pass_entry] shortcode in the Field Formula box.
Replace x with the key or ID of the field that you want to pull the value from.
Now, when the user submits the Select entry form, the fields are populated with values from the selected entry.
Use this option when your users aren't logged in and you want to pull values from another form they submitted. To do this, insert the [frm-field-value field_id=x ip=1] shortcode into the Default Value box in the field options. Replace x with the ID of the field that you want to get the value from.
If several entries have been submitted in that form from the same IP address, this shortcode gets the value from the most recent entry.
Since Formidable Forms 7.0, a logged-out visitor gets only an entry that was submitted while logged out. A logged-in user gets the latest entry from their IP address that was submitted while logged out or by their own account. Administrators get the latest entry from that IP address, whoever submitted it.
This method depends on the visitor's IP address. If the same person uses a different computer or network, for example, this shortcode doesn't find their earlier entry. Visitors on a shared network, such as an office or school, can have the same IP address and get each other's latest entry.
To pull values from a particular entry into your current form, insert the [frm-field-value field_id=x entry=1296] shortcode into the Default Value box in the field options. Replace x with the ID of the field that you want to get the value from. Replace 1296 with the ID or key of the entry that you want to pull values from.
Since Formidable Forms 7.0, the value shows only to administrators and to the logged-in user who submitted that entry. Everyone else, including logged-out visitors, sees a blank field. If the value is meant to be public, make the field public with the example to show one field's value to every visitor.
When you populate a field from a field that has separate values, frm-field-value shows the label by default. To show the saved value instead, add show="value" to the shortcode: [frm-field-value field_id=x show="value"].
To include the information submitted in the form directly in the URL, use the [get param] shortcode. Learn more about how to get a parameter from the URL.
You must log in to vote
Was this article helpful? *
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.