Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
readyOH
Frequent Visitor

Cumulative percentage (CALCULATE FUNCTION)

Hi,

 

For cumulative data, I use CALCULATE SUM AND FILTER functions. it works pretty well

For example, if i want to have the cumulative sales

SalesCumul = CALCULATE(SUM('Table1'[Sales]);FILTER(ALL('Table1'[Month]);'Table1'[Month]<= MAX('Table1'[Month])))

 

but when I want to cumulate percentage it does not work.

For example, I have a measure in percent :  SavingRate = sum(saving)/sum(purchase)

When i want to cumulate it. So

January : JanuarySavingRate

February : JanuarySavingRate + FebruarySavingRate

March : FebruarySavingRate + MarchSavingRate

etc...

 

it does not work

my formula is

CumulSavingRate = CALCULATE(SUM('Table1'[SavingRate]);FILTER(ALL('Table1'[Month]);'Table1'[Month]<= MAX('Table1'[Month])))

 

I can't find the solution

 

thanks

 

 

 

 

1 ACCEPTED SOLUTION

Ahh, so you are looking for attainment of goal.  That makes more sense now.

 

So currently, you have Column E (from your example) working - and Column F is what you are trying to solve?

 

In that case, if you need to keep static numbers for each month ( i.e. in February we had saved 5, and at that time, were at .69% of our 7% goal ) you need to use a calculated column for the SavingsCumul, not a measure.

 

Your columns will be as follows : (using pseudo-code, not actual syntax - new/changed columns bolded )

 

Savings: <fact data>

Purchase: <fact data>

SavingsCumul: calculate sum of [Savings], filtered by [month], where [month] <= [month]

MonthlySavings: [savings] / [purchase] (and then format the column as a percent)

Attainment of goal to date : [savingsCumul] / [PurchasesYTD] (format as percentage)

 

Then you can add the measure : PurchasesYTD: = calculate sum of [purchases]

 

Then you will be able to see your percentage of savings for each month, as compared to total purchases.  Keep in mind that those percentages in the Attainment column will change when you refresh your data

 

 

Below is a theoretical discussion of analytics, and not at all related to answering your question.  Feel free to ignore it if you wish.:

 

Keep in mind that those percentages in the Attainment column will change when you refresh your data ... so realistically, the only number that makes a difference in terms of tracking your KPIs, will be the last month anyways.  Not trying to be a jerk - as I don't understand your particular situation - just, as a Business Analyst, knowing how much we had saved in February as a percentage of what we sold YTD, is a useless metric.  I would be interested in knowing "how much have we saved YTD compared to purchased YTD?" - which is what your first set of measures was calculating fine.  If you need to track it over time, then it makes sense to track Cumulative Savings vs Cumulative Purchases - to find out your percentage to goal as of that month.  But doing it vs YTD doesn't make sense.

 

 

View solution in original post

3 REPLIES 3
ALeef
Resolver II
Resolver II

Try using SUMX to iterate through all the rows.  Also, while you can SUM the values, be careful what you are actually asking for.  By adding percentages, you will end up with a mostly meaningless number.  I saved 6% this month, 8% last month, and 14% the month before.  Overall did I save 28%?  Should I be averaging them instead?

 

I think what you are actually looking for is a total for the whole table of savings / purchase.  I would calculate those both cumulatively, like you did with sales - and then divide the results of those two to get cumulative SavingsRate.  

 

So you would have SavingsCumul and PurchaseCumul , and a third measure names SavingRateCumul which is SavingsCumul / PurchaseCumul.

 

Make sense?  A bit of data structure would help to visualize it.  Or you can use calculated columns at lowest granularity instead of measures to make the calcs more static.

readyOH
Frequent Visitor

@ALeef thank you.

ALeef wrote: I saved 6% this month, 8% last month, and 14% the month before.  Overall did I save 28%?  Should I be averaging them instead?

no because this will be a cumulativeSaving/TotalPurchase

 

A sample data &colon;

ABCDEF
 SavingPurchaseSavingCumul

Monthly Saving % of purchase

B/C

SavingCumul in %

B/728

January210121,98%0,27%
February310252,94%0,69%
March410393,88%1,24%
April5104144,81%1,92%
May6105205,71%2,75%
June7106276,60%3,71%
July8107357,48%4,81%
Total35728   

 

 

For example, if we have a target 7% of saving at the end of the year, thanks to my measure SavingCumul in %, I will see the gap between us and our target (my target is also a cumulative measure of my monthly targets).if we don't make cumulative, we only track month by month without knowing if we are in good way to reach the target

 

So we do this type of figures

saving%vstarget.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

@ALeef wrote:

I think what you are actually looking for is a total for the whole table of savings / purchase.  I would calculate those both cumulatively, like you did with sales - and then divide the results of those two to get cumulative SavingsRate.  

 

So you would have SavingsCumul and PurchaseCumul , and a third measure names SavingRateCumul which is SavingsCumul / PurchaseCumul.

 

Sounds great but I tried and it does not work because I have to make SavingsCumul / Total Purchase

So February for example it has to be (Saving Jan + Saving Feb) / (Total Purchase Jan to July)

and not   (Jan + Saving Feb) / (Purchase Jan + Purchase Feb)

Ahh, so you are looking for attainment of goal.  That makes more sense now.

 

So currently, you have Column E (from your example) working - and Column F is what you are trying to solve?

 

In that case, if you need to keep static numbers for each month ( i.e. in February we had saved 5, and at that time, were at .69% of our 7% goal ) you need to use a calculated column for the SavingsCumul, not a measure.

 

Your columns will be as follows : (using pseudo-code, not actual syntax - new/changed columns bolded )

 

Savings: <fact data>

Purchase: <fact data>

SavingsCumul: calculate sum of [Savings], filtered by [month], where [month] <= [month]

MonthlySavings: [savings] / [purchase] (and then format the column as a percent)

Attainment of goal to date : [savingsCumul] / [PurchasesYTD] (format as percentage)

 

Then you can add the measure : PurchasesYTD: = calculate sum of [purchases]

 

Then you will be able to see your percentage of savings for each month, as compared to total purchases.  Keep in mind that those percentages in the Attainment column will change when you refresh your data

 

 

Below is a theoretical discussion of analytics, and not at all related to answering your question.  Feel free to ignore it if you wish.:

 

Keep in mind that those percentages in the Attainment column will change when you refresh your data ... so realistically, the only number that makes a difference in terms of tracking your KPIs, will be the last month anyways.  Not trying to be a jerk - as I don't understand your particular situation - just, as a Business Analyst, knowing how much we had saved in February as a percentage of what we sold YTD, is a useless metric.  I would be interested in knowing "how much have we saved YTD compared to purchased YTD?" - which is what your first set of measures was calculating fine.  If you need to track it over time, then it makes sense to track Cumulative Savings vs Cumulative Purchases - to find out your percentage to goal as of that month.  But doing it vs YTD doesn't make sense.

 

 

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.