How to use disablePageWise Aggregates with an Async Datasource

[Unknown]

I have a grid which retrieves per page data from a webapi, when using Grouping the counts are not correct (client-side for the current page). There is an option disablePageWiseAggregates, but how to implement that in combination with an async datasource?

[Balaji Sekar]

Hi Arnaud, 

 

Greetings From Syncfusion Support. 

 

Query#: when using Grouping the counts are not correct 

 

Based on your requirement we have prepared a sample with Web API and validate your query, but unfortunately we are unable to reproduce the issue at our end. The counts value from the aggregates are  works fine while using the Grouping. Please refer the below sample, screenshot and Documentation for more information. 

 

Without Grouping                                                                                                                                                          With Grouping 

 

                             

 

 

Sample: https://stackblitz.com/edit/angular-xvtq82?file=app.component.ts 

 

Documentation: https://ej2.syncfusion.com/angular/documentation/grid/observables/#observable-binding-using-async-pipe 

                              https://ej2.syncfusion.com/angular/documentation/grid/observables/#calculate-aggregates 

 

If we misunderstood anything wrongly, Please get back us with the following details 

 

1. Please share your exact requirement scenario with brief explanation.
2. Please share your issue scenario in video demonstration.
3. If possible please reproduce the issue with our above attached sample.

 

Regards, 

Balaji Sekar. 

[Unknown]

Hi Balaji

In the example group on Ship City. On page one Albuquerque has 4 items, on page two 10 items and on page three 4 items. I aspect on every page 18 items in the header, because that is the summary.

Regards 

Arnaud

[Balaji Sekar]

Hi Arnaud, 

 

Thanks For the Update. 

 

We have analyzed your query and with the current architecture of Web API adaptor Grid, it is not feasible to achieve your requirement. Because the data fetch from the Web API based on your pageSize and returns the results and counts (Based on the OnDemand concepts). So we can’t calculate the next page grouped items in the initial stage. It was the default behavior. 

 

Regards,
Balaji Sekar.