Launched: Running Total (Cumulative Sum, Avg, Min, Max)

While 2021 is running to an end, Holistics is all about…Running Total! :man_running:

Running Total is a very common calculation method that shows how a metric changes over time e.g. how the number of goods sold accumulates over months.

Previously, you could create Running Totals using our Transform Model (guide), though that requires some SQL knowledge. Now, with just a few clicks, you can immediately create a Running Total in visualization settings. Kabam!

In this version, we support 4 types of Running Total: Sum, Average, Min, and Max.

For more information, please visit our document.


It would be great if we could also add support for count / count distinct.

That way I can (for example) count individual transaction IDs for the day, and see a running total by hour.


Hi Rob, welcome to the community!

We have supported count/count distinct already, but I assume that you want to combine it with running total right?

I’m a bit stuck at the “count ID by day, but see running total by hours”. Could you help elaborate on the expected output a lil’ bit?

1 Like

Hey Tuan!

Yeah, ideally I’d like the ability to do a running total of count distinct.
I have unique quote IDs line-by-line for our service - I can count those to get our total number of quotes over a time period - I’d like to be able to use that count as a running total too.

1 Like

Ah, I see, thanks for sharing. I’ve noted your request down for my team to discuss and consider supporting it in the future.

Also, I created a separate thread for this specific request in case others want to share their use cases too. Please help me upvote it @Rob_B to help our team prioritize our backlog better :wink:


it would be great for running total to return values even if there’s no entry in a given period. To illustrate imagine a customer who purchases a product in the last month of every quarter. The running sum of revenue for the company would be increasing every quarter if you look at the data by quarter. However if you change the view to look at running sum of revenue per month there will be nothing for the first two months of every quarter. I would prefer if the first two months showed the same value as the last month of the previous quarter, rather than showing nothing.


Hi there,

Is there a reason to only compute running totals on date dimensions ? I have some usecases where it would be useful to calculate running totals on any numeric value.

For example, I would like to visualise the distribution of my users by quantity of documents produced each year. I would like to calculate the running sum of users by quantity of documents produced in order to visualize where are my top and bottom 10% users.


Totally agree with you that we should be showing the current running sum for the first two months.

The reason Holistics is not showing the number is it’s treating the first two months as having NULL data instead of 0, so the calculation will skip those months and jump straight to the final month of the quarter. That means the key issue is related to how NULL is handled (and converted) in Holistics. We’ve had a plan to work on this project very soon. Will let you know when there are any new updates!

Ah, the current running total is still in its early days, and we are collecting more feedback and ideas to improve it i.e. adding new ways to calculate it.

I still have some trouble visualizing your use case. Could you help share a demo piece of data and how you’d like to visualize it?

Hi @tuan.nguyen ,

We did the analysis below that can be used as an example :

We manipulate a database of customer orders composed of one or more lines of orders and wanted to know how many lines were created for each order. So we made the following chart :

It says that 40% or orders have 1 single line, 22% have 2 lines, …

Then, we wanted to know, if we had to limit the number of lines possible for each order, what would be an acceptable value. That’s where the cumulated sum chart is useful :

This chart does not show values on datapoints but it says that if we fix the limit to 30 lines, we cover more than 99% of orders.

I hope this helps,


Thanks for the great example @dacou !

In order to visualize the cumulated sum chart you sent, I imagine our data should be structured like this:

Num of lines Num of orders Cumulative sum of orders Percent of total Cumulative percent
1 100 100 40% 40%
2 20 120 20% 60%
3 5 125 10% 70%
33 1 200 1% 99%

Then we will visualize the Num of lines and the Cumulative percent on the chart.

Am I close?

Exactly, except for a typo on the first line (Cumulative sum of orders = 100) :wink:

1 Like

Got it @dacou , fixed :wink: