Open RivaIvanova opened 1 year ago
Hello,
I would like to know when this bug will be corrected. Is there any upcoming release that includes the correction? It's still not working for us, and it's critical for our operations.
Thank you.
@IsiAymeric , please have in mind that 22.2 is no longer supported and while we plan to release a fix soon, it will only be available in 23.1 and 23.2
Description
When grouping by a column of type
date
and applying additional summary configurations for other columns, the results differ when usingmin
ormax
aggregate functions.Consider the following configuration:
The summary result displays the value![igGridSummariesMin](https://github.com/IgniteUI/ignite-ui/assets/49126110/5fe2fc25-1a7c-4927-8998-890d85239958)
1/1/1970
:However, when setting to another aggregate function, for example,
avg
,the result is the following:![igGridSummariesAvg](https://github.com/IgniteUI/ignite-ui/assets/49126110/c2c5c822-c78f-4bab-b178-ef7d63ab3809)
This is due to the following check in the![igGridSummaries](https://github.com/IgniteUI/ignite-ui/assets/49126110/a4339c4d-6bdd-44f0-b406-c9d046f5ee3c)
_summaries
function:Steps to reproduce
Result
The results differ when using
min
ormax
aggregate functions.Expected result
The results should be a number representing the
min
ormax
value inside the column.