<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Validating a field on submit</title><link>https://community.appian.com/discussions/f/general/20301/validating-a-field-on-submit</link><description>I have a component that contains user picker field which is a required field. This component also has a submit button. Something like the code snippet below. 
 
 
 
 
 Now, I&amp;#39;m calling this component inside a foreach loop in the parent form. 
 foreach</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Validating a field on submit</title><link>https://community.appian.com/thread/79199?ContentTypeID=1</link><pubDate>Wed, 27 Jan 2021 21:40:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c8edaadc-644d-4051-9cf2-67b4de1bb134</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;I suppose you could use ValidationGroup settings on your fields and buttons... just make each ValidationGroup unique per your current location in the array you&amp;#39;re using to generate the repeated section.&amp;nbsp; I&amp;#39;ve traditionally avoided validationGroup on buttons since it works a little clunkily (such as, the &amp;quot;required&amp;quot; asterisks are no longer shown when a field has a validationGroup), but it would probably work here.&amp;nbsp; If you can&amp;#39;t forego the &amp;quot;required&amp;quot; asterisks, my main alternative suggestion would be to simply disable the button in a particular section unless the required fields are filled.&amp;nbsp; Then you just set the &amp;quot;validate&amp;quot; parameter of the button to FALSE.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Validating a field on submit</title><link>https://community.appian.com/thread/79198?ContentTypeID=1</link><pubDate>Wed, 27 Jan 2021 21:33:03 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ca3062f5-a7e8-4c5d-b22f-c216e6650a39</guid><dc:creator>Jose H.</dc:creator><description>&lt;p&gt;Mike, the goal is that there is a list of items, but the user can only approve one of them at a time. The following screenshot shows what the interface looks like.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/11/pastedimage1611783266877v1.png" alt=" " /&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Validating a field on submit</title><link>https://community.appian.com/thread/79197?ContentTypeID=1</link><pubDate>Wed, 27 Jan 2021 21:24:01 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0f3571ae-3795-402b-b03c-348ed6df79ce</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;What do you hope to accomplish in using a repeating list of pickers and buttons, where all buttons submit the form?&amp;nbsp; Because the form will still be submitted regardless of which of those buttons you click.&amp;nbsp; Why wouldn&amp;#39;t you have the individual fields save into a list, and then have the user submit the form based on a single submit button when you&amp;#39;ve determined through on-form logic that a sufficient number of picker fields have been populated?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>