Hello Brian Graves,
This behavior is by design.
When you want to page a grouped grid the behavior is too ambiguous: should the grid group only the items in the current page, or group all the items and have the pager split one group in several pages?
What should happen if the page size is set to 1 for example. Should this get only one record? Or only one group? In other words, there is no clear logic about paging a grouped grid, or grouping a paged grid if you prefer.
You can think of paging occurring first (i.e. get a "PageSize" number of entities from a DomainDataSource for example). After
the data (i.e. page 1 containing 10 records) has "arrived" on the client grouping is performed over this and only this data. In other words, the grid is not aware of the large-scale picture -- it only knows about 10 records at a time, it does not know that this is part of a larger set of data residing on the server for example. That is why it is grouping what it currently has as its items source, which is page one containing the 10 records.
I hope this makes sense.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.