<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Dynamic Population from previous form</title>
		<link>https://legacy.forums.gravityhelp.com/topic/dynamic-population-from-previous-form</link>
		<description>Gravity Support Forums Topic: Dynamic Population from previous form</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 02:55:31 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/dynamic-population-from-previous-form" rel="self" type="application/rss+xml" />

		<item>
			<title>Rob Harrell on "Dynamic Population from previous form"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dynamic-population-from-previous-form#post-72231</link>
			<pubDate>Thu, 23 Aug 2012 08:30:54 +0000</pubDate>
			<dc:creator>Rob Harrell</dc:creator>
			<guid isPermaLink="false">72231@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Yes and yes. You can do this with dynamic population and query strings. In the &#34;sidebar&#34; form you will setup the confirmation redirect (in the form's settings) to go to the page with the &#34;more information&#34; form. On this form you will have the two fields in question checked to by dynamically populated (which is in the advanced tab of each field). Give each a parameter name that you'd like to identify them with (no spaces, but you can use underscores). Then back on your side bar form, in the confirmation url redirect setting, you would enable the query string and then place your paramater names with the values you will get from using the merge tag drop down. For example:&#60;/p&#62;
&#60;p&#62;name={MergeTag1}&#38;amp;email={MergeTag2}&#60;/p&#62;
&#60;p&#62;This will append to the url of the more information form, so when they go there, those two fields will be populated accordingly.&#60;/p&#62;
&#60;p&#62;If a user is already logged into your site, you can use our user merge tags to place in the &#34;default value&#34; of each field that would pertain to user meta. See this page (user section):&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.gravityhelp.com/documentation/page/Merge_Tags&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/page/Merge_Tags&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>TimmyD on "Dynamic Population from previous form"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dynamic-population-from-previous-form#post-72223</link>
			<pubDate>Thu, 23 Aug 2012 07:58:41 +0000</pubDate>
			<dc:creator>TimmyD</dc:creator>
			<guid isPermaLink="false">72223@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I'm a little confused as to how query strings or dynamic population can help in this scenario.&#60;/p&#62;
&#60;p&#62;The aim to have someone sign up to a newsletter with just a name and email on one form - imagine that sitting on a sidebar of an article. On submission they are then taken off to another form - on a whole page - in an attempt to collect more data i.e. preferences if they wish to provide them.&#60;/p&#62;
&#60;p&#62;What's the best method of ensuring that the second form, to collect preferences, automatically populates both the name and email fields.&#60;/p&#62;
&#60;p&#62;On the same note, is a similar solution possible where auto populating fields based on a signed in user's info is concerned. e.g. user signs into website and when accessing a similar preference page, the fields are populated based on the users email, username etc.&#60;/p&#62;
&#60;p&#62;Many thanks in advance
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
