asked on May 11, 2022
Hi,
I found an issue about wrong computation of aggregate values.
Here's a JSFiddle: we have a hierarchy field in the columns, and the second element on the rows is filtered by two elements. Look for example at the Australia/Warehouse value (attached Img1). If you expand the second level then this value is wrong (attached Img2).
The issue seems to be related to hierarchy field. Indeed, if you define the BuinessType and Color as separate simple fields the value is right.
Thank you in advance,
Ilaria
⋅ May 11, 2022
Hello, Ilaria!
Thank you for reporting this issue.
We will take a look at the described expanding behavior and provide a fix with our minor release with the ETA May 30th.
Best Regards,
Maksym
⋅ May 31, 2022
Hello, Ilaria,
We are glad to announce that the issue with wrong values when expanding filtered child having hierarchy field is fixed. The fix is provided in the new minor release (v. 2.9.26) of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please contact us in case any questions arise.
Best Regards,
Maksym
⋅ June 7, 2022
Hello, Ilaria,
We would like to know whether you had a chance to check if our fix is working. Looking forward to hearing from you.
Best Regards,
Maksym
⋅ June 14, 2022
Hi, Ilaria!
Our team is wondering whether you had time to test the fix. Please let us know if it works for you.
Best Regards,
Maksym
⋅ June 30, 2022
Hi Maksym!
Sorry for my late answer but I have been trying the fix in our environment and it doesn't work properly yet, whilst the JSFiddle I linked in my first request in perfectly working. I noticed that the payload of the 'select' request changed a little bit in your last release. Do you confirm I have to modify my server implementation to complete the fix?
Thank you!
Ilaria
⋅ July 1, 2022
Hello, Ilaria!
Thank you for your reply.
We want to explain that the fix did not impose any changes to the custom data source protocol itself - the response structure remains the same as before. The only difference is that the result on the grid is achieved by multiple select requests: Flexmonster makes several /select requests, each targeting different parts, and their intersection provides the correct visualization. With this in mind, we suggest making sure that your custom data source API implementation handles such a scenario.
Please let us know if this helps to get everything working. As always, feel free to write to us if any questions arise.
Best Regards,
Maksym
