Hi Stanisław,
do you mean with last 100 rows that you want to have some kind of paging in the item list, to load the additional data, if the user wants to see it?
Regardless, I just improved the loading time of on of hour forms this week. In regards to the item list you have two main points.
- Loading time
This is the time of the "Getting model of workflow element (/api/nav/db/1/app/11/element/165/desktop)' row in the diagnostic mode
- Rendering time
This is the time of the creation of the HTML elements. Unfortunately, there no dedicated log for this.
Loading time
If you have choose columns with SQL in them, make sure that you don't reference fields of the item list row, if possible. This will execute one SQL statement for each row and field. Even if the SQL server would just take 2ms for the execution, it would be 2400+ms in your case. But the more connection there are, the slower it gets.
It's the same for data row columns, but I'm not sure whether there's a chance to reduce the number of SQL statements send to the server.
A data table will be execute in a single SQL statement and is therefore way faster when using data row columns.
As long as the item list is not hidden server side, field matrix or visibility restriction, it's data will be loaded. Hiding it via form rules is to late to prevent it.
Rendering time
If you don't need to display the item list by default, move it to a tab, so that it is not rendered. Unfortunately, WEBCON removed the option to render read only columns in an item list as plain text. Now always a deactivated input field is created. Due to this change the rendering of the data table elements is also faster then rendering an item list. Of course, you can add paging to it.
Best regards,
Daniel