<?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>Editable grid with required fields and Add and Remove buttons of type submit.</title><link>https://community.appian.com/discussions/f/user-interface/13269/editable-grid-with-required-fields-and-add-and-remove-buttons-of-type-submit</link><description>Hi, 
 We have a Use case like 
 Editable grid having 3 required fields of type like Name(text), Salary(float), commisstion(float), 
 Two Buttons of type Submit like AddEmployee and RemoveEmployee,(not inline add and delete buttons with editable grid)</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Editable grid with required fields and Add and Remove buttons of type submit.</title><link>https://community.appian.com/thread/59975?ContentTypeID=1</link><pubDate>Wed, 05 Sep 2018 03:13:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b2523082-f306-47fe-9306-f62201cb9468</guid><dc:creator>josep</dc:creator><description>I haven’t tried it with the editable grid, but maybe something like this multiple validstionGroups can help&lt;br /&gt;
&lt;br /&gt;
&lt;a href="https://community.appian.com/discussions/f/user-interface/12730/need-to-make-a-field-is-required-for-a-button-which-has-skipped-all-the-validation-including-this-field"&gt;community.appian.com/.../need-to-make-a-field-is-required-for-a-button-which-has-skipped-all-the-validation-including-this-field&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Jose&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Editable grid with required fields and Add and Remove buttons of type submit.</title><link>https://community.appian.com/thread/59961?ContentTypeID=1</link><pubDate>Tue, 04 Sep 2018 22:30:31 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6f5c9e97-b1b8-47f8-8d11-2def1f2133dc</guid><dc:creator>gianninol</dc:creator><description>&lt;p&gt;It sounds to me like the use of validation groups (&lt;a href="https://docs.appian.com/suite/help/18.3/recipe_use_validation_group_for_buttons_with_multiple_validation_rules.html" target="_blank"&gt;example here&lt;/a&gt;). By adding a validation group to a field, that field will only validate if a button or link with the same validation group is pressed. By assigning the &amp;quot;RemoveEmployee&amp;quot; validation group to the validation in Case1, it won&amp;#39;t trigger until that link is clicked. Likewise, the link will not validate the requiredness of the fields that do not have the &amp;quot;RemoveEmployee&amp;quot; validation group.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>