Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi all,
I have the following code that summarizes the existing table in my dataset and performs some calculations.
Then I want that second table to be summarized based on one column and then return the sum of a newly created column.
I think that the answer to my problem might be obvious but I cannot seem to figure it out.
Using the below expressions I get for each date the total Weighted Transactions for all dates while I would want that to be for each AsOfDate.
Here is how the dax expession looks like:
Solved! Go to Solution.
Hi @FotFly - your DAX expression to ensure the grouping within the SUMMARIZE is scoped correctly
Modified the dax as below:
VAR Trans =
ADDCOLUMNS(
Transactions,
"Weight",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
),
"WeightedTrans",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
) * Transactions[CashAmount $]
)
VAR SumWeightTrans =
SUMMARIZE(
Trans,
Trans[AsOfDate],
"SumWeightedTrans",
SUMX(
FILTER(Trans, Trans[AsOfDate] = EARLIER(Trans[AsOfDate])),
[WeightedTrans]
)
)
RETURN
SumWeightTrans
I hope this result in the correct sum of WeightedTrans grouped by AsOfDate.
Proud to be a Super User! | |
Try
SummaryTable =
VAR Trans =
ADDCOLUMNS (
SUMMARIZE ( Transactions, Transactions[EffectiveDate], Transactions[AsOfDate] ),
"@Cash Amount $", CALCULATE ( SUM ( Transactions[CashAmount $] ) ),
"@WeightedTrans",
DIVIDE (
DATEDIFF ( Transactions[EffectiveDate], Transactions[AsOfDate], DAY ),
DATEDIFF ( EOMONTH ( Transactions[AsOfDate], -3 ), Transactions[AsOfDate], DAY )
) * [@CashAmount $]
)
VAR SumWeightTrans =
GROUPBY (
Trans,
[AsOfDate],
"@SumWeightedTrans", SUMX ( CURRENTGROUP (), [@WeightedTrans] )
)
RETURN
SumWeightReturns
The main point is to use GROUPBY rather than the second SUMMARIZE, but I've also tweaked the code a bit.
You should never use SUMMARIZE to add calculated columns, just use that for grouping and use ADDCOLUMNS to add the new columns you need.
I've also removed the Weight column as it wasn't being used, so there's no point calculating it.
Finally, I use @ in column names in temporary tables, so that they are easily distinguishable from columns or measures in the model.
Here’s the corrected DAX expression:
VAR Trans =
SUMMARIZE(
Transactions,
Transactions[EffectiveDate],
Transactions[AsOfDate],
Transactions[CashAmount $],
"Weight",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
),
"WeightedTrans",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
) * Transactions[CashAmount $]
)
VAR SumWeightTrans =
SUMMARIZE(
Trans,
[AsOfDate],
"SumWeightedTrans",
SUMX(
CURRENTGROUP(), -- Use CURRENTGROUP() to reference the rows within each AsOfDate group
[WeightedTrans]
)
)
RETURN
SumWeightTrans
💌 If this helped, a Kudos 👍 or Solution mark would be great! 🎉
Cheers,
Kedar
Connect on LinkedIn
Try
SummaryTable =
VAR Trans =
ADDCOLUMNS (
SUMMARIZE ( Transactions, Transactions[EffectiveDate], Transactions[AsOfDate] ),
"@Cash Amount $", CALCULATE ( SUM ( Transactions[CashAmount $] ) ),
"@WeightedTrans",
DIVIDE (
DATEDIFF ( Transactions[EffectiveDate], Transactions[AsOfDate], DAY ),
DATEDIFF ( EOMONTH ( Transactions[AsOfDate], -3 ), Transactions[AsOfDate], DAY )
) * [@CashAmount $]
)
VAR SumWeightTrans =
GROUPBY (
Trans,
[AsOfDate],
"@SumWeightedTrans", SUMX ( CURRENTGROUP (), [@WeightedTrans] )
)
RETURN
SumWeightReturns
The main point is to use GROUPBY rather than the second SUMMARIZE, but I've also tweaked the code a bit.
You should never use SUMMARIZE to add calculated columns, just use that for grouping and use ADDCOLUMNS to add the new columns you need.
I've also removed the Weight column as it wasn't being used, so there's no point calculating it.
Finally, I use @ in column names in temporary tables, so that they are easily distinguishable from columns or measures in the model.
Thank you very much! I will test is out. This is a different approach that I havent thought.
Hi @FotFly - your DAX expression to ensure the grouping within the SUMMARIZE is scoped correctly
Modified the dax as below:
VAR Trans =
ADDCOLUMNS(
Transactions,
"Weight",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
),
"WeightedTrans",
DIVIDE(
DATEDIFF(Transactions[EffectiveDate], Transactions[AsOfDate], DAY),
DATEDIFF(EOMONTH(Transactions[AsOfDate], -3), Transactions[AsOfDate], DAY)
) * Transactions[CashAmount $]
)
VAR SumWeightTrans =
SUMMARIZE(
Trans,
Trans[AsOfDate],
"SumWeightedTrans",
SUMX(
FILTER(Trans, Trans[AsOfDate] = EARLIER(Trans[AsOfDate])),
[WeightedTrans]
)
)
RETURN
SumWeightTrans
I hope this result in the correct sum of WeightedTrans grouped by AsOfDate.
Proud to be a Super User! | |
Thank you very much!
I tried that version with filter before but it was the earlier part that I was missing. I was trying to find an expression that could actually function with my virtual table column while filtering.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
81 | |
75 | |
60 | |
37 | |
33 |
User | Count |
---|---|
102 | |
56 | |
52 | |
46 | |
40 |