asked on January 13, 2022
Hey Team,
As I'm getting Maximum call stack size exceeded error due to choosing the aggregation of "percentofparentrowtotal".
I've attached a stackblitz link.
https://stackblitz.com/edit/angular-ivy-p6yrbf?file=src/app/app.component.ts
⋅ January 13, 2022
Hello, Ravi,
Thank you for reporting this issue and for sharing a stackblitz example.
It seems the error occurs if all of the grid values are zeros (0). If different values are present, everything seems to be working as expected when a percent aggregation is selected.
Our team will look into the issue in more detail and provide the fix with a minor update, ETA 7th of February. We will share the results once the minor release is available.
In the meantime, feel free to reach out to us if questions arise.
Kind regards,
Vera
⋅ January 27, 2022
Hey Vera Didenko,
Thanks for the update.
Nevertheless, we are currently using version 2.9.2. It is not possible to update the latest version. Because we have to check a lot of use cases before pushing them to production. At the same time, we have limited time to update.
So Could you please fix this particular bug in the v2.9.2 itself?
⋅ January 27, 2022
Hello, Ravi,
Thank you for your reply.
We understand your concerns regarding updating the component’s version.
Due to our internal procedures, unfortunately, we cannot provide fixes to our older versions. All of our further updates (such as improvements and fixes for known and reported issues) are introduced with a scheduled bi-weekly release. Consequently, the fix is planned for the nearest available minor release.
At the same time, due to Flexmonster’s backward compatibility and since major changes are only introduced in major releases, updating to the latest minor release version of 2.9 shouldn’t introduce breaking changes.
Our team relies on your understanding.
Kind regards,
Vera
⋅ February 7, 2022
Hello, Ravi,
Hope all is well!
We are happy to inform you that our team fixed the issue with the percent aggregation formula when data contains only zeroes.
This is available in the 2.9.18 (latest) minor release version of Flexmonster.
You are welcome to update the component.
Please let us know if the fix works fine for you.
We are looking forward to your confirmation.
Kind regards,
Vera
⋅ February 15, 2022
Hello, Ravi,
Hope you are doing well.
We were wondering if you had some time to test the fix.
Is everything working well on your end, or is there something we can help you with?
Looking forward to your reply.
Kind regards,
Vera
⋅ March 4, 2022
Hi Vera Didenko,
We got the fix and it is working in the 2.9.18. but as I was afraid it is getting broke in some other features that are customized from our side.
and we have found an issue in custom sorting. that fix is also one of the blockers for our production deployment.
ticket is: Custom sortorder is not working properly • Flexmonster
So we need the mentioned 2 fixes in the version: 2.9.2 itself. it is very important for us to deploy for our customer go-live.
So please consider this is the highest priority from our side and provide the solution that helps us to make customers go-live.
⋅ March 7, 2022
Hello, Ravi,
Thank you for your response.
We are happy to hear that updating to 2.9.18 fixed the issue with the percent aggregation formula.
As for the new issue with custom sorting, our team is currently working on the fix with the ETA 21st of March. We will keep you updated on the matter.
About providing both fixes to an older version of Flexmonster 2.9.2, I am afraid we don't have the possibility to provide fixes to our older versions as explained before. Please consider that each subsequent minor version is an improved version of the previous one. Moreover, each new version also undergoes regression testing, ensuring that previous features and functionality remain intact.
Thank you for your understanding.
Kind regards,
Vera
This question is now closed
