<?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: Checkboxes add data column?</title>
		<link>https://legacy.forums.gravityhelp.com/topic/checkboxes-add-data-column</link>
		<description>Gravity Support Forums Topic: Checkboxes add data column?</description>
		<language>en-US</language>
		<pubDate>Fri, 17 Apr 2026 02:28:00 +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/checkboxes-add-data-column" rel="self" type="application/rss+xml" />

		<item>
			<title>jajo on "Checkboxes add data column?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/checkboxes-add-data-column#post-1188</link>
			<pubDate>Mon, 26 Oct 2009 17:26:50 +0000</pubDate>
			<dc:creator>jajo</dc:creator>
			<guid isPermaLink="false">1188@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I did notice that they are also ungrouped in the export, which is my primary concern. Its not really an issue on the current project however, but if there were an option whether or not to group checkbox results in both the list and the export, in a future release, that'd be fantastic.&#60;/p&#62;
&#60;p&#62;I should mention, that is my only complaint so far! We've got two projects in the cooker that GF is being used on, and has saved us a TON of time!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Checkboxes add data column?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/checkboxes-add-data-column#post-1186</link>
			<pubDate>Mon, 26 Oct 2009 17:20:00 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">1186@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;You are correct, checkboxes, even when grouped act as separate fields on the Entry List page. This is by design.  It has uses for simple forms where you can quickly see which options they checked, however it does begin to break down when you put many fields on the Entry List page using the column customizer.&#60;/p&#62;
&#60;p&#62;The Entry List page only has so much screen real estate anyway, because you only have so much horizontal screen space. So it is best to only list the most important columns on the Entry List page and save the rest for the detail page itself.&#60;/p&#62;
&#60;p&#62;Checkboxes are grouped together under one field on the Entry Detail page when viewing a specific Entry and they are also grouped together in the Notification emails.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>jajo on "Checkboxes add data column?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/checkboxes-add-data-column#post-1183</link>
			<pubDate>Mon, 26 Oct 2009 16:26:09 +0000</pubDate>
			<dc:creator>jajo</dc:creator>
			<guid isPermaLink="false">1183@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I recently added a checkbox set to my form, with a couple options.&#60;/p&#62;
&#60;p&#62;I noticed when entries are submitted to this, instead of bundling all the values for that checkbox under a single value, and comma delimiting the values or something, it is, instead creating individual columns for each selected value, with the value being equal to the column header.&#60;/p&#62;
&#60;p&#62;Is this the intended function? If so, wouldn't that prevent you from having two separate checkbox sets with the same value as an option, since you wouldn't be able to tell which was which in the admin (and you can't re-Admin-label checkbox values, only the 'container', which doesn't seem to be used in the Entries at all).
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
