When I click on a table that contains more than 100 records, the browser hangs for 10-20 seconds before showing the content and becoming responsive, the longest 10-20 seconds of the day. They feel even longer if I want to see another table and I’m forced to wait anyway.
Is it possible to decrease the number of rows to 10 or to make it user definable?
I am interested in something like this - where the first 20 rows of a data table load, then user can click a ‘NEXT’ button to display the next 20. This might be able to be done today programmatically, but I’m not quite sure how. And I wouldn’t want it to slow down the app loading either, as my home page currently takes about 10-12 seconds, I’d like that to be cut in half.
I’ve found the load time to be noticeably less in Firefox than Chrome - do you get the same effect?
Ah yes that’s a bit slower than I’m seeing!
I have the same FR: Decrease the default number of rows displayed on a table
I always use Chrome and I noticed that the time it takes to show the same first 100 rows of the same table can vary anywhere between 5 and 30 seconds.
I always try to create the columns and configure the table before adding data. Then, after the table has too much data in it, I try to avoid showing it, or I show it only once in the morning.
Right now I have a large slow table on my app. I don’t need anymore to modify the columns, but I still need to look at the data as I test the app. I open a second tab on the same app, show that table once in the morning, then I use the download button to download the whole table or manually edit just the values visible on the first page.
YAY!!!
The request has been satisfied: it is now possible to select a small number of visible rows from a drop down above the dable.