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

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
Thigs
Helper IV
Helper IV

Incorrect result - SUMX two tables

Hi all, 

I am working with SUMX for the first time and with two different tables.

 

Yes, I have look at other similar posts, and my formula isn't throwing errors, but it isn't getting the correct result. 

 

I have two tables - Dimensions has a SKU number, height, weight, length and width. Each SKU is unique

Orders has Order Number, SKU number, quantity, and then several other columns not needed for this calculation. 

 

I am trying to figure out the average weight of orders per day. 

 

Here is my formula - 

New Measure Try = sumx(Orders, Orders[Quantity] * AVERAGE('Dimensions'[weight]))
 
This is getting larger numbers than when I do it in Excel. Is the "Average" the issue? I can't seem to tell it to do SUMX without using some kind of calculation for the second table. The two tables have a one-many relationship, with Dimensions being the one. 
 
Any help is super appreciated!
1 ACCEPTED SOLUTION
OwenAuger
Super User
Super User

Hi @Thigs 

Based on what you've described, here is what I would suggest if I were creating these calculations:

 

Create these measures:

Order Quantity =
SUM ( Orders[Quantity] )
Total Weight =
SUMX (
    SUMMARIZE ( Orders, 'Dimensions'[weight] ),
    'Dimensions'[weight] * [Order Quantity]
)

The Total Weight measure takes the distinct weights for SKUs appearing in the Orders table, and multiplies these by the corresponding Order Quantity and sums.

 

Then for the average weight, did you want the average weight per order?

You would first need a measure that returns the Order Count, either by counting distinct Order Numbers, or counting rows of Orders (whichever is correct), i.e.:

Order Count =
DISTINCTCOUNT ( Orders[Order Number] )

or

Order Count =
COUNTROWS ( Orders )

Then the average weight per order would be:

Order Average Weight =
DIVIDE ( [Total Weight], [Order Count] )

 

Does the above help get the result you were looking for?

Please post back if needed.

 

Regards,

Owen

 


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
LinkedIn

View solution in original post

2 REPLIES 2
OwenAuger
Super User
Super User

Hi @Thigs 

Based on what you've described, here is what I would suggest if I were creating these calculations:

 

Create these measures:

Order Quantity =
SUM ( Orders[Quantity] )
Total Weight =
SUMX (
    SUMMARIZE ( Orders, 'Dimensions'[weight] ),
    'Dimensions'[weight] * [Order Quantity]
)

The Total Weight measure takes the distinct weights for SKUs appearing in the Orders table, and multiplies these by the corresponding Order Quantity and sums.

 

Then for the average weight, did you want the average weight per order?

You would first need a measure that returns the Order Count, either by counting distinct Order Numbers, or counting rows of Orders (whichever is correct), i.e.:

Order Count =
DISTINCTCOUNT ( Orders[Order Number] )

or

Order Count =
COUNTROWS ( Orders )

Then the average weight per order would be:

Order Average Weight =
DIVIDE ( [Total Weight], [Order Count] )

 

Does the above help get the result you were looking for?

Please post back if needed.

 

Regards,

Owen

 


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
LinkedIn

Ah! Perfect! Thanks SO much!

 

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.