<?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: Collecting Contact Info for Multiple People</title>
		<link>https://legacy.forums.gravityhelp.com/topic/collecting-contact-info-for-multiple-people</link>
		<description>Gravity Support Forums Topic: Collecting Contact Info for Multiple People</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 03:26:30 +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/collecting-contact-info-for-multiple-people" rel="self" type="application/rss+xml" />

		<item>
			<title>David Peralty on "Collecting Contact Info for Multiple People"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/collecting-contact-info-for-multiple-people#post-345935</link>
			<pubDate>Wed, 26 Jun 2013 11:18:57 +0000</pubDate>
			<dc:creator>David Peralty</dc:creator>
			<guid isPermaLink="false">345935@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Yeah, repeatable fieldsets is a highly requested feature. The data integration is SUPER difficult though. If you've ever used our list field, and exported the data, you'd see what I mean. It is really difficult to set-up the database table structure to be flexible. Even the entries page might look odd with some having lots of information and others having very little.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>VFHwebdev on "Collecting Contact Info for Multiple People"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/collecting-contact-info-for-multiple-people#post-345918</link>
			<pubDate>Wed, 26 Jun 2013 11:06:11 +0000</pubDate>
			<dc:creator>VFHwebdev</dc:creator>
			<guid isPermaLink="false">345918@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;So if we wanted to allow people to purchase up to 10 tickets for example, we'd set up 10 sets of contact fields and show/hide them based on the quantity? That's kind of what I was thinking.&#60;/p&#62;
&#60;p&#62;You can't apply conditional logic to the default quantity field of a product, but it looks like you can for the separate quantity field.&#60;/p&#62;
&#60;p&#62;For a future feature request, it would be fabulous if you could set up &#34;repeater&#34; fields and tie them to the quantity field. That way we could create a contact info section and have that section repeat based on the number of tickets purchased.&#60;/p&#62;
&#60;p&#62;I suspect that would be useful for other types of forms (not just events) too.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>David Peralty on "Collecting Contact Info for Multiple People"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/collecting-contact-info-for-multiple-people#post-345909</link>
			<pubDate>Wed, 26 Jun 2013 11:00:28 +0000</pubDate>
			<dc:creator>David Peralty</dc:creator>
			<guid isPermaLink="false">345909@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I would have a drop down that says &#34;How many tickets&#34; and then I would have fields for your maximum number all on the form, but hidden using conditional logic. Each set could say something like &#34;Show this field if Tickets is less than 4&#34; etc...
&#60;/p&#62;</description>
		</item>
		<item>
			<title>VFHwebdev on "Collecting Contact Info for Multiple People"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/collecting-contact-info-for-multiple-people#post-345903</link>
			<pubDate>Wed, 26 Jun 2013 10:55:02 +0000</pubDate>
			<dc:creator>VFHwebdev</dc:creator>
			<guid isPermaLink="false">345903@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I'm using Gravity Forms to build some event registration forms. In a lot of cases one person is buying and paying for tickets for multiple people. &#60;/p&#62;
&#60;p&#62;We'd like to collect basic contact information for all the attendees, not just the ticket buyer.&#60;/p&#62;
&#60;p&#62;But I can't figure out the best way to do that. What would you recommend? &#60;/p&#62;
&#60;p&#62;If someone is only buying one ticket I don't want them to be presented with contact fields for 10 people. &#60;/p&#62;
&#60;p&#62;Thanks!
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
