Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi Community..!!
| Order No. | Tot. Order Value Gross | Bus. Unit Code | @@test |
| 1549751713 | 33260 | 10 | 33260 |
| 1557865412 | 91944.46 | 10 | 91944.46 |
| 1557893444 | 31963 | 10 | 31963 |
i have above data, @@test is my measure, i need row wise calculation, after adding total order values gross i am getting 275,833 which is wrong , addition of these values should be = 33260 + 91944 + 31963 = 157167
this is my measure
Kindly help me on the same.
Solved! Go to Solution.
Hi @prasadpatil020,
The problem is not the SUMX itself but how the row context / filters are evaluated (and sometimes duplicate rows) which makes the MAX() return unexpected values or cause double-counting.
Try below DAX, it creates a virtual table and then sums up the data.
@@test =
SUMX(
SUMMARIZE(
'Order Level Details',
'Order Level Details'[Order No],
"OrderVal", MAX('Order Level Details'[Tot. Order Value Gross])
),
[OrderVal]
)
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
I'm glad you found a solution! We're here in the community to support each other.
Regards,
Rufyda Rahma | Microsoft MIE
@@test = SUM('Order Level Details'[Tot. Order Value Gross])
Why: Simple SUM respects row context naturally and totals correctly (157167).
If this answer helped, please click Kudos or Accept as Solution.
-Kedar
LinkedIn: https://www.linkedin.com/in/kedar-pande
Hi @prasadpatil020,
The problem is not the SUMX itself but how the row context / filters are evaluated (and sometimes duplicate rows) which makes the MAX() return unexpected values or cause double-counting.
Try below DAX, it creates a virtual table and then sums up the data.
@@test =
SUMX(
SUMMARIZE(
'Order Level Details',
'Order Level Details'[Order No],
"OrderVal", MAX('Order Level Details'[Tot. Order Value Gross])
),
[OrderVal]
)
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
If 'Order No.' is unique in your table, you can simply use:
@@test = SUM('Order Level Details'[Tot. Order Value Gross])
If there are duplicate order numbers and you want to sum only the maximum value per order, your measure is close, but you should check your data for duplicates
DAX
@@test =
SUMX(
VALUES('Order Level Details'[Order No.]),
MAX('Order Level Details'[Tot. Order Value Gross])
)
This will work if, for each 'Order No.', the MAX returns the correct value (which is the only value if there are no duplicates). But if your table has multiple rows per order with different 'Tot. Order Value Gross'
Proud to be a Super User! |
|
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 63 | |
| 55 | |
| 42 | |
| 41 | |
| 23 |
| User | Count |
|---|---|
| 167 | |
| 136 | |
| 120 | |
| 79 | |
| 54 |