Given a table Sales with columns Quantity and UnitPrice, what is the result of this DAX measure?
Measure = SUMX(Sales, Sales[Quantity] * Sales[UnitPrice])
Assume the table has these rows:
- Quantity: 2, UnitPrice: 10
- Quantity: 3, UnitPrice: 15
- Quantity: 1, UnitPrice: 20
Measure = SUMX(Sales, Sales[Quantity] * Sales[UnitPrice])
Multiply quantity by unit price for each row, then add all results.
Row 1: 2*10=20, Row 2: 3*15=45, Row 3: 1*20=20; Total = 20+45+20 = 85.
You have a measure using SUMX to calculate total sales per product category. Which visualization best shows the sales distribution across categories?
Think about showing parts of a whole for categories.
A pie chart clearly shows how total sales are divided among categories, matching the SUMX measure per category.
What error occurs with this DAX measure?
Measure = SUMX(FILTER(Sales, Sales[Quantity] > 2), Sales[Quantity] * Sales[UnitPrice])
Assume Sales table has rows with Quantity values 1, 2, 3.
Measure = SUMX(FILTER(Sales, Sales[Quantity] > 2), Sales[Quantity] * Sales[UnitPrice])FILTER returns rows where Quantity is greater than 2.
FILTER returns rows with Quantity > 2 (only Quantity=3), SUMX multiplies and sums those rows correctly.
You have two tables: Orders with columns OrderID, CustomerID, and Quantity, and Products with columns ProductID, CustomerID, and UnitPrice. You want to calculate total sales per customer using SUMX. Which DAX measure correctly calculates this?
Use RELATED to get unit price from Products for each order row.
Option B correctly multiplies quantity by unit price using RELATED to access Products data per order row.
Which statement best explains why SUMX is preferred over SUM when calculating total sales as Quantity * UnitPrice?
Think about how calculations happen per row.
SUMX iterates each row to calculate Quantity * UnitPrice before summing, SUM only sums one column's values without row-wise calculation.