asked on February 28, 2024
Hi,
I noticed that if you have hierarchical field and you define a formula with running totals, the formula shows the wrong values after expand all.
Here is a JSFiddle to reproduce the issue.
If you click on expand all, 2023/01 has value=5 but it should be 1: it seems that the formula is computing running total without considering the hierarrchy.
The issue is not present if you expand manually the year 2023, instead.
Could you please solve the issue?
Thank you in advance,
Ilaria
⋅ February 29, 2024
Hello, Ilaria!
Thank you for reaching out to us and providing a reproducible JSFiddle.
Our dev team will look closer at the described behavior of calculating running totals with multilevel hierarchies and get back to you with a fix with the ETA March 18th.
We will notify you about any updates on the matter.
Kind regards,
Solomiia
⋅ March 19, 2024
Hello, Ilaria!
Hope everything is well.
We are happy to inform you that the issue with the wrong running totals calculation for multilevel hierarchies when the expandAll property is enabled was fixed.
The fix is included in 2.9.73 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-73/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if the fix works well for you.
Kind regards,
Solomiia
⋅ March 26, 2024
Hi Solomiia,
unfotunately the issue is not completely solved: if you have for example a three level (or more) hierarchy, after expand the intermediate levels only the firtst running totals are correct.
Here the modified JSfiddle
Please notice that the issue is present both on 'json' datasource and 'custom' datasource.
Thany you in advance
Ilaria
⋅ March 26, 2024
Hello, Ilaria!
Thank you for your feedback and the provided JSFIddle.
Our Dev team will test the calculation of running totals on more nested levels and get back to you with the fix with ETA on April 15th.
We will notify you as soon as the update is ready.
Kind regards,
Solomiia
⋅ April 11, 2024
Hello, Ilaria!
Hope you are doing well.
Our Dev team has tested the provided JSFiddle with running totals example and hasn't found the inconsistency in calculations. Kindly note that since there is no option of setting the level of running totals calculation in Flexmonster, running totals are calculated on all levels, which may be the cause of misunderstanding. For example, in the provided JSFiddle, the Q2 value is a sum of the Q1 running total value(3) and its own running total(1).
Hope you will find our answer helpful.
Best regards,
Solomiia
⋅ September 18, 2025
Hi Solomiia,
sorry for the huge delay in getting back to you.
The calculation on the quarter side makes sense, but it doesn’t on the months: for example, in 2023/04 I would expect to see the cumulative value of the previous months — so not 1, but 4.
If I put only month in the pivot, for 2023/04 I do see the correct value: 4, which is the cumulative of all months up to April 2023.
The value of a cell should not change depending on the higher-level aggregation applied above it. The cumulative should be calculated level by level.
Please find attached an image with the expected value.
Thanks!
Ilaria
⋅ September 19, 2025
Hello, Ilaria!
Thank you for getting back to us.
Kindly note that running totals in multilevel hierarchies can be calculated in different ways. In Flexmonster, running totals are calculated on all levels, and for the lowest hierarchy level they are calculated separately. For example, if Month is the last level of the hierarchy, the running total is calculated across all Q1 Months and then restarted from zero for Q2 Months.
We understand that this approach may not fully align with your expectations. However, please note that this is the default behavior in Flexmonster.
Hope it helps.
Kind regards,
Solomiia
