You have two tables: Sales with columns OrderID, ProductID, and Quantity, and Products with columns ProductID and Price. You want to create a calculated column in Sales that shows the total sales amount per order line by multiplying Quantity by the Price from Products.
Which DAX formula correctly uses RELATED to get the Price from the Products table?
Remember, RELATED fetches a value from a related table using an existing relationship.
Option A correctly multiplies the Quantity in Sales by the Price from the related Products table using RELATED(Products[Price]). Option A tries to get Price from the same table, which doesn't exist. Option A reverses the tables incorrectly. Option A uses LOOKUPVALUE, which works but is less efficient than RELATED when a relationship exists.
You have a Customers table and an Orders table related by CustomerID. You want to create a report showing each customer's name and the total number of orders they placed.
Which visualization and measure setup best uses RELATED or related concepts to display this information?
Think about how to count related rows from another table.
Option C correctly uses RELATEDTABLE to count all orders related to each customer. Option C uses Customer Name from Orders, which may duplicate customers. Option C counts orders but does not filter by customer context properly. Option C tries to use RELATED on a one-to-many side, which is invalid.
In Power BI, the RELATED function retrieves a value from a related table. Which statement best describes the direction in which RELATED works in a data model?
Think about which table has the unique key and which has multiple rows.
RELATED works from the 'many' side to the 'one' side in a one-to-many relationship, meaning it fetches a single related value from the 'one' side table. Option A correctly states this. Option A reverses the direction. Option A is incorrect because RELATED does not work with many-to-many relationships. Option A is incorrect because RELATED accesses other tables.
You wrote this calculated column formula in the Orders table:
Customer City = RELATED(Customers[City])
But you get an error: "The expression refers to multiple columns. Multiple columns cannot be converted to a scalar value."
What is the most likely cause of this error?
Check if the tables are connected properly.
The error usually occurs when RELATED cannot find a single related row because no relationship exists between the tables. Option D is correct. Option D is invalid because RELATED expects a single value, but the error message points to missing relationship, not multiple values. Option D is incorrect because RELATED must be used on the 'many' side. Option D is invalid because RELATED requires a column, not a table.
You have three tables: Sales (with OrderID, ProductID, Quantity), Products (with ProductID, CategoryID, Price), and Categories (with CategoryID, CategoryName). Relationships are Sales → Products (many-to-one) and Products → Categories (many-to-one).
You want to create a measure that calculates the total sales amount for a selected category by multiplying Quantity by Price and filtering by CategoryName.
Which DAX measure correctly uses RELATED to achieve this?
Remember that RELATED works from many-to-one, and filtering should be done on the correct table.
Option B correctly filters the Products table by CategoryName from Categories and calculates total sales using RELATED(Products[Price]) in Sales. Option B incorrectly uses RELATED in a filter condition that is invalid. Option B tries to use RELATED on Categories from Products but the filter context is not properly set. Option B applies filters on Sales with multiple RELATED calls causing errors.