Getting few bugs in the code

RE: Getting few bugs in the code

varunkumarb0001 — Wed, 12 Feb 2020 18:39:15 GMT

Yes, that's the one I was looking for, You saved my day, Thanks Mike...

RE: Getting few bugs in the code

Mike Schmitt — Wed, 12 Feb 2020 18:16:43 GMT

Does this post seem to describe behavior matching what you're observing? It's probably the one I was thinking of.

RE: Getting few bugs in the code

varunkumarb0001 — Wed, 12 Feb 2020 18:10:05 GMT

Sure Thanks...

RE: Getting few bugs in the code

Mike Schmitt — Wed, 12 Feb 2020 18:09:11 GMT

I may have heard about this before - if so there's a chance that it's a known bug within Appian. Not "expected behavior" of course but perhaps something they know about. If I can find the previous thread here where someone else reported it (assuming i remember right) i'll try to post it here.

RE: Getting few bugs in the code

varunkumarb0001 — Wed, 12 Feb 2020 18:07:42 GMT

This case is with every first required grid column, it doesn't show up red border around it whether you make it required or not, I think default behavior of Appian

RE: Getting few bugs in the code

varunkumarb0001 — Wed, 12 Feb 2020 17:36:18 GMT

I've all issues sorted out but there's a weird issue that I have dropdown field also as required field but while submitting the form every unfilled required field is coming with red border except that dropdown but it's validating but not getting red. Can you help with what I could be missing? Above is the whole code which I'm using...

RE: Getting few bugs in the code

varunkumarb0001 — Wed, 12 Feb 2020 09:28:31 GMT

Thanks Mike, got your point...

RE: Getting few bugs in the code

Mike Schmitt — Tue, 11 Feb 2020 19:35:28 GMT

The first issue is tougher - in general, if you mark individual fields in an editable grid as Required and/or have other validations on them, then each individual field will display its failed validation status when the user tries to submit the form. There's no single answer for an easy way around this, other than perhaps experimenting and seeing if you can come up with a reasonable compromise. For instance, you could turn off the "required" setting for a particular field, and instead add a section-level or form-level validation that checks to make sure there are no blank entries for that field within the CDT array that you're saving into. This of course has pros and cons, since individual fields that are missing or have a failed validation state won't be individually called out by the form.

RE: Getting few bugs in the code

varunkumarb0001 — Tue, 11 Feb 2020 19:24:12 GMT

Thanks @Mike, can we do something for the first one?

RE: Getting few bugs in the code

Mike Schmitt — Tue, 11 Feb 2020 18:40:42 GMT

[quote userid="38067" url="~/discussions/f/general/18306/getting-few-bugs-in-the-code"]Second issue is related to the first one, when user for example, first deletes any of the row using "X" and then again generates the new row back using add row link, validation message automatically appears for that, which shouldn't be the case. Below captured video shows the issue.[/quote]

I believe the behavior you're seeing here is expected behavior. Once the validation condition has been triggered, all valid validation messages will show up instantly until the form is validated (and for any given field, the validation message should disappear once its conditions are met). This is simply the way validations work on SAIL forms.