Skip to main content

Problem Statement: Calculated fields in report builder only perform calculations on a row level. 

Solution: Functionality is needed to do a calculation after an aggregation / group-by happens in the report. 

Workaround: For any metrics that needs to be calcuated by a different aggregation (CSM, Region, Sub Region, Country, and more) we will have to build individual data designers to show the correct number. This solution also prevents us from having drill downs that let you drill down into the company data within a certain data point. We will need to have one report for the aggregation and then a table next to it for the company row level data. This is not scalable.…

 

Having this functionality would make calculated fields in report builder a complete game changer and limit the need for data designers to perform calculations like this 

 

Example data set

 

Upvoting this! 

This exact use case has always been a pain for us over the years and we haven’t found better workaround than @jsiudzinski_uber described, of using Data designer (or rules engine populating a new table), losing the ability to drilldown on the data. Or worse yet, not just drill down but properly filter the data.

 

I’m not sure if there’s a better workaround that we’ve missed, because this has been such a recurring scenario for us that I can’t help but feel that there is a better way to do this.

This is needed to calculate GRR and NRR data.

 

Unless there is a workaround I am missing…

Best,

Ben Wanless

YES PLEASE.

 

I just had to build out an entire custom MDA and a series of rules to update it specifically because I cannot run post-aggregation formulas in report builder directly. Huge nasty time sink.

Quick Update:

I actually was looking at the Create Formula and noticed the Sum() function… which is an aggregation! And lo and behold it actually worked the way I expected. It first summed the column values and then performed the mathematical operation to produce the correct result.

I still need to double check that it works as expected when I apply filters, but this is promising.

Terms & ConditionsCookie settingsAccessibility statement