Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi all,
Here is a Christmas brain cracker for our DAX specialists!
I want to create a DAX measure that calculates the percentage of values per category in a table to the total of that table, with the following custom rounding:
- All percentages need to be rounded down to the nearest integer.
- Then it needs to be identified how much percentage points are missing to reach the 100% in total.
- Next, these percentage points need to be added each to the percentages with the largest decimal part in descending order.
Please note the dataset is huge so the impact of the DAX calculation should be limited as much as possible
So for example:
Category A: 26.98%,
Category B: 34.78%,
Category C: 38.24%
Rounded down this becomes:
Category A: 26
Category B: 34
Category C: 38
26 + 34 + 38 = 98 -> 2 missing percentage points
These missing percentage points need to be assigned to the 2 percentages with the highest decimal part:
Category A: 27
Category B: 35
Category C: 38
27 + 35 + 38 = 100%
How can I do this with DAX? I think some iteration and /or buffering is required, but how do I do this?
@parry2k maybe you know?
Solved! Go to Solution.
@PunchBird I have modified things to be more in line with your data and requirements. See if this works. Updated PBIX is attached below signature.
Measure 2 =
VAR __Cat2 = MAX('Table'[Category2])
VAR __Table =
GENERATE(
SUMMARIZE(
FILTER(ALLSELECTED('Table'), [Category2] = __Cat2),
'Table'[Category1],'Table'[Category2],"Value",MAX([Percentage])),
VAR __Value = [Value]
VAR __RD = ROUNDDOWN(__Value,0)
VAR __Decimal = __Value - __RD
RETURN
ROW(
"RD", __RD,
"Decimal", __Decimal
)
)
VAR __MaxDecimal = MAXX(__Table,[Decimal])
VAR __MaxCategory = MAXX(FILTER(__Table, [Decimal] = __MaxDecimal),[Category1])
VAR __2ndMaxDecimal = MAXX(FILTER(__Table, [Category1] <> __MaxCategory), [Decimal])
VAR __2ndMaxCategory = MAXX(FILTER(__Table, [Category1] <> __MaxCategory && [Decimal] = __2ndMaxDecimal),[Category1])
VAR __Category = MAX('Table'[Category1])
VAR __Result =
IF(
__Category = __MaxCategory || __Category = __2ndMaxCategory,
ROUNDUP(MAX([Percentage]),0),
ROUNDDOWN(MAX([Percentage]),0)
)
RETURN
__Result //CONCATENATEX(__Table, [Category1]&":"&[Category2]&":"&[Value]&":"&[RD]&":"&[Decimal],UNICHAR(10)&UNICHAR(13))
@PunchBird Easy fix for that, see below and attached PBIX.
Measure 2 =
VAR __Cat2 = MAX('Table'[Category2])
VAR __Table =
GENERATE(
SUMMARIZE(
FILTER(ALLSELECTED('Table'), [Category2] = __Cat2),
'Table'[Category1],'Table'[Category2],"Value",MAX([Percentage])),
VAR __Value = [Value]
VAR __RD = ROUNDDOWN(__Value,0)
VAR __Decimal = __Value - __RD
RETURN
ROW(
"RD", __RD,
"Decimal", __Decimal
)
)
VAR __MaxDecimal = MAXX(__Table,[Decimal])
VAR __MaxCategory = MAXX(FILTER(__Table, [Decimal] = __MaxDecimal),[Category1])
VAR __2ndMaxDecimal = MAXX(FILTER(__Table, [Category1] <> __MaxCategory), [Decimal])
VAR __2ndMaxCategory = MAXX(FILTER(__Table, [Category1] <> __MaxCategory && [Decimal] = __2ndMaxDecimal),[Category1])
VAR __Category = MAX('Table'[Category1])
VAR __SumDown = SUMX(__Table, [RD])
VAR __Result =
SWITCH(__SumDown,
99,
IF(
__Category = __MaxCategory,
ROUNDUP(MAX([Percentage]),0),
ROUNDDOWN(MAX([Percentage]),0)
),
98,
IF(
__Category = __MaxCategory || __Category = __2ndMaxCategory,
ROUNDUP(MAX([Percentage]),0),
ROUNDDOWN(MAX([Percentage]),0)
)
)
RETURN
__Result //CONCATENATEX(__Table, [Category1]&":"&[Category2]&":"&[Value]&":"&[RD]&":"&[Decimal],UNICHAR(10)&UNICHAR(13))
Great, that worked! Thanks so much, very much appreciated 🙂
And I added an alternative for SWITCH in case nothing needs to be rounded (in the unlikely case all are numbers with 0 decimals)
I can prepare Power Query M for rounddown or roundup solution, but without this additional req to split this % value between Category 2 or 3. Sorry. 🙂
Proud to be a Super User!
I see you worked a tie into the example data. Please see this updated measure expression that uses RAND to break the tie.
AdjValue =
VAR vThisVal = [AvgVal]
VAR vThisCategory1 =
MIN ( T1[Category1] )
VAR tNew =
ADDCOLUMNS (
CALCULATETABLE ( DISTINCT ( T1[Category1] ), REMOVEFILTERS ( T1[Category1] ) ),
"cOrigVal", [AvgVal]
)
VAR tRoundMod =
ADDCOLUMNS (
tNew,
"cRD", ROUNDDOWN ( [cOrigVal], 0 ),
"cMod", MOD ( [cOrigVal], 1 ),
"cRand", RAND()/1000
)
VAR vThisModRand = SUMX(FILTER(tRoundMod, T1[Category1] = vThisCategory1), [cMod] + [cRand])
VAR vGapTo100 =
100 - SUMX ( tRoundMod, [cRD] )
VAR vModRank =
RANKX ( tRoundMod, [cMod] + [cRand], vThisModRand, DESC )
VAR vResult =
IF ( vModRank <= vGapTo100, ROUNDUP ( vThisVal, 0 ), ROUNDDOWN ( vThisVal, 0 ) )
RETURN
vResult
Pat
Hi Pat @ppm1 I tested this on my simple test dataset, and noticed the results are correct! However, it seems that the values assigned to the ties (B and C in Category1) are very instable, i.e. when I refresh the report the values change every time, see screenshots below in column TEST. Maybe this has something to do with the results stored in a virtual table?
After refresh:
@PunchBird Ah! so remainder distribution is dynamic.
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
yes indeed!
Here's a measure expression that shows one way to do it. You'll have to watch out for ties in the MOD values, and for when the values add up to >100 (but you can adapt this measure to do that).
AdjValue =
VAR vThisCategory =
MIN ( T1[Category] )
VAR vThisVal = [AvgVal]
VAR vThisRD =
ROUNDDOWN ( vThisVal, 0 )
VAR vThisMod =
MOD ( vThisVal, 1 )
VAR tNew =
ADDCOLUMNS ( ALL ( T1[Category] ), "cOrigVal", [AvgVal] )
VAR tRoundMod =
ADDCOLUMNS (
tNew,
"cRD", ROUNDDOWN ( [cOrigVal], 0 ),
"cMod", MOD ( [cOrigVal], 1 )
)
VAR vGapTo100 =
100 - SUMX ( tRoundMod, [cRD] )
VAR vModRank =
RANKX ( SELECTCOLUMNS ( tRoundMod, "cMod2", [cMod] ), [cMod2], vThisMod, DESC )
VAR vResult =
IF ( vModRank <= vGapTo100, ROUNDUP ( vThisVal, 0 ), ROUNDDOWN ( vThisVal, 0 ) )
RETURN
vResult
Pat
@PunchBird I did this (see below). PBIX is attached.
Measure =
VAR __Table =
GENERATE(
SUMMARIZE(ALLSELECTED('Table'),'Table'[Category]),
VAR __Value = [Percentage]
VAR __RD = ROUNDDOWN(__Value,2)
VAR __Decimal = __Value - __RD
RETURN
ROW(
"Value", __Value,
"RD", __RD,
"Decimal", __Decimal
)
)
VAR __MaxDecimal = MAXX(__Table,[Decimal])
VAR __MaxCategory = MAXX(FILTER(__Table, [Decimal] = __MaxDecimal),[Category])
VAR __Category = MAX('Table'[Category])
VAR __Result = IF(__Category = __MaxCategory, ROUNDUP([Percentage],2), ROUNDDOWN([Percentage],2))
RETURN
__Result
@Greg_Deckler thanks for your calculation. I tested this on my testdata (see below for more elaborate example), but apparently your calculation only works when there is one percent point to be added. If there are two percent points that need to be added, the total is 99%, see also screenshot below. Maybe I could use a for- or while loop, like you described here?
@PunchBird Interesting question. Does the remainder always get equally distributed to the top two contributors?
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
@parry2k the remainder needs to be distributed in descending order. So if the remainder is 1, it is assigned to the percentage that had largest decimal part, and if the remainder is 2, it is assigned to the two top percentages that had largest decimal part
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
89 | |
86 | |
82 | |
64 | |
49 |
User | Count |
---|---|
125 | |
111 | |
88 | |
69 | |
66 |