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
  • I think it depends on your specific use case. I had a situation where it could return a lot of rows, so I didn't want the user to have to enter lots of data and suffer loosing it if they forgot to submit etc. So I changed my query to only return first 25 then got the user to complete the first 25 then click save and this then updates the table etc and if all the items have been completed the process ends otherwise it loops back round and then brings the next 25 etc.

    My use case was quite simple and suited this approach and I also let them search for certain records and only update these ones within the grid.
Reply
  • I think it depends on your specific use case. I had a situation where it could return a lot of rows, so I didn't want the user to have to enter lots of data and suffer loosing it if they forgot to submit etc. So I changed my query to only return first 25 then got the user to complete the first 25 then click save and this then updates the table etc and if all the items have been completed the process ends otherwise it loops back round and then brings the next 25 etc.

    My use case was quite simple and suited this approach and I also let them search for certain records and only update these ones within the grid.
Children
No Data