Hi Renard,
Thanks for your update.
By default, grouping virtualization operates on the basis of blocks that are initially allowed to load and render rows only from the content viewport (pageSettings.pageSize). After scrolling, the next set of page records is made. For this case, if we reaches scroller to the bottom, grid may rendered rows less number of records.
For example: If we use total records as 1000 and pageSize as 30, initially 30 rows of grid render rows ad when scrolling down its render next set of 30 rows. Likewise if we reaches bottom (1000%30 = 10) it’s rendered only 10 rows but space allocated for next 30 rows. So we suspect your reported issue may occurs this reason.
We cannot replicate the recorded problem when using pageSize as 52 (includes aggregate row also) based on total rows. Please refer to the following sample for reference.
To overcome this issue we suggest to use infinite scrolling instead of virtual scrolling. Infinite scrolling is used to load a huge amount of data without degrading the Grid performance. This feature works like the lazy loading concept, which means the buffer data is loaded only when the scrollbar reaches the end of the scroller.
Please get back to us, if you need any further assistance.
Regards,
Thiyagu S