Hi Isomorphic,
I have a question or perhaps enhancement suggestion.
You do still load the 1st 1000 rows by default for a grouped ListGrid when using ListGrid.setSortByGroupFirst().
The number 1000 is the ListGrid.setGroupByMaxRecords()-default.
On the one hand it affects the fetch issued with respect to the requested rows (0-1000) on the other hand it does what the name says - prevent ListGrids with more than the specified rows from grouping (see this sample, where the group-options are disabled in the header menu).
With ListGrid.setSortByGroupFirst() enabled, you should be able to have normal setDataPageSize() requests (default 0-75) and still have grouping (with no limit), shouldn't you?
This is what I tried to suggest here.
Special case (new rows while scrolling could belong somewhere in the middle, not at the end) might be with fields with setGroupValueFunction() (or it might just not possible with these fields).
Best regards,
Blama
I have a question or perhaps enhancement suggestion.
You do still load the 1st 1000 rows by default for a grouped ListGrid when using ListGrid.setSortByGroupFirst().
The number 1000 is the ListGrid.setGroupByMaxRecords()-default.
On the one hand it affects the fetch issued with respect to the requested rows (0-1000) on the other hand it does what the name says - prevent ListGrids with more than the specified rows from grouping (see this sample, where the group-options are disabled in the header menu).
With ListGrid.setSortByGroupFirst() enabled, you should be able to have normal setDataPageSize() requests (default 0-75) and still have grouping (with no limit), shouldn't you?
This is what I tried to suggest here.
Special case (new rows while scrolling could belong somewhere in the middle, not at the end) might be with fields with setGroupValueFunction() (or it might just not possible with these fields).
Best regards,
Blama
Comment