I have a BAQ that I show on my layout. The BAQ grid has grouping and advanced grid filters turned on. There is a strange behavior at the subtotals when filtering and expand/collapsing the groups. In this example you can see the group total are correct, and the grand total is correct. As soon as I expand each group the group subtotals go all wild. I do the same test for Production and Setup labor records so you can see it twice.
Is this working as designed?
We have seen a lot of problems with grouping on dashboards like that. We had some conditional coloring on certain fields that, once we grouped, got all kinds of messed up.
The grouping and ungrouping also appears to have some performance issues when dealing with large amounts of data - our browsers have locked up frequently. I avoid grouping altogether and just bring it out to Excel if I need to aggregate given these issues.
Does it work if you turn off server paging? Make it always get all rows?
I think this is a dashboard option. This is not a dash just a BAQ deployed as a layout.
It happens on a dashboard grid with old filter feature as well. Appears to be another of many broken client-side grid issues. Appears to work if you can get the ExecuteBaq to do the aggregates server-side.
Like group then filter then refresh grid from grid actions. This seems to kick it into server-side mode (sometimes) you’ll notice it starts to ExcuteBaq request twice per group-expand.
Unfortunately, they spent resources to doing all this SQL and extra server trips instead of just making the client-side kendo grid built-in aggregation work as intended.
Ouch. Client-side story is worse than I thought. When the grid switches to server-side mode, and you expand a group, only data from exanded groups is in the dataview.
This is NOT howie dewitt ladies and gentlemen.
