Slow Performance when Validations in Editable Grid

Hi Karthik,
The inline field validations by means of complex expression rules would definitely degrade the grid performance. Alternatively you could try out all the validations at one go on click of a button -or- you could limit the page size to 20 and go for inline validations for that page.
Thanks,
Smruti

Hi Karthik,
Agree with Smruti. Please limit the page side and go with inline validation. Also check your validation expression rule performance and try try to optimize.
Performance is a known challenge for a bigger row size grid in Appian. One more way is that you can minimize or break your validations few on grid and few on submission.
Thank you.

Can you provide an example of your sail code if allowed?

Hi karthikk640 there can be multiple reasons behind slow performance as mention below:

1. If you server is having too much of load or let's say due to multiple applications, users and requests server is not responding properly, in such case you can restart the server, or can increase its configuration.

2. Execution of multiple if() or nested if() can also cause performance issue. To avoid this you can perform all these validations on button submit, i.e. form level validation.

3. Do not query multiple/all rows at a time instead query in batch size of 10, and in Such case you need to create a section, to customise pagination for editable grid, as Appian do not have pagination available OOTB for an editable grid. In fact if you do this, then I believe performing multiple validation on each cell modification, won't impact the performance much.

4. Try to avoid with() as much as you can

5. If possible, do not perform db operation in with()

Hope this will help you to enhance your interface performance

Hi Smruti,
We have to show the validations immediately/Dynamically once user enters the values. I cannot perform validations on a button as per my use case. Let me know your thoughts on this.

Hi Alok,
Each row in a grid contains different set of validations,so we are performing validations based on Index.Let me know your thoughts on this.

Hello Karthik,

We were also facing performance issue due to many validations and logical filtering, we are now moving that validation and filtering in DB.

1. If possible you can perform some validation on DB itself.
2. By defining the batch size you can minimize the performance issue but not to full, you have to look into your expression rule and try to optimize it, if not then its better to do some validation. at DB side.

Thanks
Sahil

Hi Sahil,
Thank you very much for your response. We are performing inline validations in editable grid. As per your approach i think we have to hit the table and validate on it each time when user enter values. Correct me if am wrong?

But I believe If user is entering many value and then you are hitting database .Then I thing it will also not good approach. Firstly you have to analyze how much minimum time user will enter the value.

Hi Karthik, if you validation is based on rows but not on column, then you can do following to avoid multiple times processing while field unfocus over the grid.

1. On button submit, perform loop over array of rows (editable grid rows)

2. Check for necessary conditions, if the validation criteria didn't meet, throw a validation message using a!validationmessage()

In this approach, you can avoid multiple time processing whenever you are done with a particular row. And entire validation will take place at once during the form submit.