Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
When you create a Running Sum metric in Developer and you want to use it on a report with Custom Groups, the values are not calculated correctly. In Developer, when creating a Running Sum metric, you can only select from existing objects, to specify the Break By and Sort By parameters.
When you use the Running Sum metric with an existing attribute for example, it calculates correctly. The problem comes in when you want to use a custom group on your report – you cannot choose a custom group in the Break By parameter. From within a dossier however, you can create a Running Sum metric and have more options available when selecting the Break By and Sort By parameters. (Rows, Columns, Cell, etc.). These options allow for correct calculation of running sums when using a custom group.
Typical use cases would be when creating a financial statement, like a balance sheet which uses custom groups to display the various general ledger items in the correct groups. In this article, I will use a different example for illustration and also provide a workaround to get it working in Developer.
RunningSum<BreakBy={Subcategory}, SortBy= (Month) >([Units Received])
and should be the sum of the Units Received + Running Sum.


Now, add this custom group to the report and remove the Subcategory. The running sum is now completely inflated:






