ListGrid requests rows twice (2nd time with strange range), even though it already has all rows from the ResultSet

[Blama]

Hi Isomorphic,

creating another testcase I noticed strange behavior with ListGrid-startup. Using the exact testcase from #1 here in v11.1p_2018-02-16, these requests are fired on startup.

I'd expect only one of the ListGrid-requests. Also, the unexpected 2nd request has a strange row-range, and the whole ResultSet is only totalRows:12 and already completely loaded with the 1st request.




Best regards
Blama

[Isomorphic]

We see the behavior you describe, but we're still considering the correct optimization to avoid it. Without the filter you have in your sample, the second fetch would actually return useful records needed to render the grid. Unfortunately, it's issued before the first fetch returns and reveals that there are only 12 rows.

We'll update this thread when a fix is made, or more information is available.

[Isomorphic]

We've made adjustments to SGWT 6.1p/SC 11.1p and newer releases to avoid a double fetch in this situation. Note that you may also find that adjusting the dataPageSize can be useful in such situations.

The fix will be in the nightly builds dated 2018-03-01 and beyond.