Hi All, I am using editable grid to display records that are fetched

Hi All,

I am using editable grid to display records that are fetched using webservice.
one of the method returns 4000 records which slows down SAIL interface.
Any idea or workaround to overcome this issue?

OriginalPostID-175417

OriginalPostID-175417

  Discussion posts and replies are publicly visible

Parents
  • Given the quantity of data being returned, I assume users may not always want to edit every row individually. If that's the case, another approach is to return data (again, by page) and display it first in a paging grid from which users can select rows to edit. The user can then edit the selected rows a-handful-at-a-time in an editable grid that would appear after the user opts to edit the selected rows. When the user clicks "Save," the paging grid is updated with the modified rows and the editable grid disappears.

    Alternatively, if it is sensible given the use case, it may improve both performance and user experience to allow bulk editing at some higher level of granularity, rather than for each line item.
Reply
  • Given the quantity of data being returned, I assume users may not always want to edit every row individually. If that's the case, another approach is to return data (again, by page) and display it first in a paging grid from which users can select rows to edit. The user can then edit the selected rows a-handful-at-a-time in an editable grid that would appear after the user opts to edit the selected rows. When the user clicks "Save," the paging grid is updated with the modified rows and the editable grid disappears.

    Alternatively, if it is sensible given the use case, it may improve both performance and user experience to allow bulk editing at some higher level of granularity, rather than for each line item.
Children
No Data