asked on October 21, 2025
Hello,
I am using a calculated metric to output the result of an If expression, which outputs a '1' per row when the condition is met and a null value when it is not met. The If expression is using values from a separate external report that is then populating them into the Flexmonster instance. However, the running total/aggregation for the '1' values do not add up to a correct subtotal across the rows inside the calculated metric column, and instead convey the same '1' value for any primary rows containing sub-rows with a '1'.
Has anything changed in the last 3-4 years to support this or is there another workaround I can try? Will this be available in a future release.
Cited ticket with a similar question/request: https://www.flexmonster.com/question/running-totals-of-calculated-value/
Thanks for any insights you can provide!
⋅ October 22, 2025
Hello,
Thank you for reaching out to us.
We recommend using the individual property for the "< 3%" calculated measure. For your formula, it makes the calculation work per individual value (i.e., for each row or cell), and then the total is shown as the sum of all these particular results.
On the contrary, when individual: true is not set, the formula behaves differently for totals. It performs aggregation based on already aggregated values. In your case, it uses the sums of "CustomColumn26" and "CustomColumn27", which leads to a different result (always "1" or empty).
We have prepared an example showing a similar formula illustrating this approach: https://jsfiddle.net/flexmonster/cyvoe982/
Note that the individual property is only available for CSV and JSON data sources.
Please let us know if the suggested approach works for you.
Best regards,
Maksym
⋅ October 30, 2025
Hello,
Hope you are doing well.
We are wondering if you tried the suggested solution by enabling the individual property to achieve the necessary results for calculated values.
Looking forward to hearing your feedback.
Best regards,
Maksym
⋅ November 18, 2025
Hello,
Just checking in to ask if you had time to try the suggested approach with individual: true for calculated values.
Please let us know if it worked for you.
Best regards,
Maksym
⋅ January 8, 2026
Hey Maksym,
Thanks again for the previously supplied answers/follow-up, we're still assessing next steps with this approach as we troubleshoot interpreting calculated values with other column types/suppliers as they're supplied from our database. In the next 2-3 months I would expect we'll have our findings and may have additional questions at that point- though I'm hoping we'll have this resolved at that time based on your recommendation.
Thanks again! - Chris C.
⋅ January 12, 2026
Hello, Chris,
Thank you for sharing this with us.
Feel free to contact us if any further assistance is needed.
Best regards,
Maksym
