Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
7 subscribers
Views
1203 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
#SAILform #editableGrid Hi all, We have found an issue that once
praveenj
over 9 years ago
#SAILform #editableGrid
Hi all,
We have found an issue that once a form has failed to submit due to a validation error, the validation on fields in subsequent new rows in an editable grid is automatically triggered. Wanted to check if this is a known issue and if there any work around at all.
Below are the steps to replicate the issue:
1. Use this editable grid recipe as an example.
forum.appian.com/.../SAIL_Recipes.html
2. Note how when the form is rendered for the first time the due date on first row has validation error.
3. Try to submit the form by clicking on "submit" button and you will see validation error continues to exists.
4. Clear the validation error by choosing the date in future. This will get rid of the validation error.
5. Add new row by clicking on "+Add Item" link.
6. Notice how the validation on summary field in this new row is triggered automatically even bef...
OriginalPostID-138894
OriginalPostID-138894
Discussion posts and replies are publicly visible
Parents
0
Tim
Certified Lead Developer
over 9 years ago
This appears to be default behavior, or is at least consistent with standard SAIL fields. As a comparison create a SAIL form with multiple required text fields, some of them hidden based on a value condition. Hit submit and see the required field errors, then trigger the hidden fields to appear - they will also have the required error despite not being active at the time of the button press. The form will be in an invalid state and therefore all validation errors will fire for rendered fields.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Tim
Certified Lead Developer
over 9 years ago
This appears to be default behavior, or is at least consistent with standard SAIL fields. As a comparison create a SAIL form with multiple required text fields, some of them hidden based on a value condition. Hit submit and see the required field errors, then trigger the hidden fields to appear - they will also have the required error despite not being active at the time of the button press. The form will be in an invalid state and therefore all validation errors will fire for rendered fields.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data