Looking for solution on editable grid performance

Question

Hi Everyone, 
 I have an editable grid with 200 rows and in line validations and calculations on each field, we will also calculating the Totals of each column in the last row of the grid. 
 What is the best way to implement this? 
 Few solutions are: 
 
 Dividing the grid into multiple parts i.e 20 rows in each grid (Even though performance is better page will take lot of time to load) 
 Diving the grid into multiple tabs 20 rows in each tab(using rich text fields).This may not be better user experience , user have to go through each tab and check for validations. 
 We can add paging by manipulating data in CDT and using rich text fields. This may not be better using experience, if there is error in last rows user have to click on next 10 times.

Please suggest any approaches which can make performance better. 
 Note:as per our use case Inline validations is mandatory, cannot validate on click of button. 
 
 Thanks in Advance

Ashvin Kapur · Answer

Karthik - There are several different ways to solve this issue. Firstly, for the calculations on the bottom row - do these need to be dynamic anytime something is updated? If it's a 200 row grid, it's unlikely that the user is scrolling to the bottom every time. Instead, you could have a button or link that when selected calculates the sums. Secondly, what types of inline validations are you doing? Your second option could work - you could display an indicator next to the tab links (or make them red) when an error is evaluated in that section (by creating a validation framework outside of Appian standard. You could also do it through a milestone field with links to each step of the entry process. For your last option, of adding paging, you could theoretically add an option to page to the last page etc. so the user wouldn't have to click next 10 times.

aloks0189 · Answer

Hi karthikk640 as per my understanding, you can opt for option no. 3 mention by you, i.e. represent the data in the form of batching and make the use of customised pagingInfo as we do not have pagingInfo available OOTB for an editable grid which you already have mention. Now answering to your problem statement, you can define 4 richtextdisplayfield ( < , <<, >, >>) where 2 for moving to next or previous batch, and 2 for moving to first or last batch, in this way user can avoid clicking on next link for several times in order to reach till last set of data. And this is achievable. You just need to play around pagingInfo, start index and batch size Hope this will help you.