Please excuse us for the delayed reply. We reviewed your scenario and we can discuss some customziations to achieve the desired results. I will try to shed some more light on waht is happening under the hood. RadGridView relies on the ICollectionView and IEditableCollection view interfaces to process its data. Additionally it uses the IQueryable interface to execute queries over its bound data source. RadDataPager relies on IPagedCollectionView to utilize paging. If the bound source collection does not implement these interfaces, both controls wrap it in a instance of QueryableCollectionView, which is one of the core collections of our data engine. Then the same instance is used by both controls to add data descriptors, or apply paging to it. However, as soon as such changes are made, all of the defined operations are then sequentially applied:
protected virtual IQueryable CreateView()
if (this.TotalItemCount == 0)
var queryable = this.QueryableSourceCollection;
queryable = queryable.Where(this.FilterDescriptors);
queryable = this.Sort(queryable);
queryable = queryable.GroupBy(this.GroupDescriptors);
queryable = queryable.Page(this.PageIndex, this.PageSize);
We have a demo that treats a similar scenario of paging befire grouping: demos
> RadGridView > Paging before grouping.
Can you please have a look at it and tell us whether a similar customization would be applicable in your scenario. We can assist you wtih the concrete implementation if it is needed.
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 Feedback Portal
and vote to affect the priority of the items