Which function defines crossfiltering direction of a physical relationship?

Which function defines crossfiltering direction of a physical relationship?

• A. PATH()
• B. CROSSFILTER()
• C. USERELATIONSHIP()
• D. TREATAS()

Answer: (B)

Filters flowing between related tables are controlled by CROSSFILTER. It lets you specify how filtering should propagate between two tables, choosing either a single direction or bidirectional flow. This is exactly what defines the cross-filtering direction for a relationship, allowing you to override the default model behavior when you need filters to travel from one side to the other (or both ways) in your calculations. The other options serve different purposes: PATH builds a path in a parent-child hierarchy, not the filtering direction between two tables; USERELATIONSHIP activates a particular relationship in a measure without changing its inherent direction; TREATAS maps values from one table to another to apply filters when there isn’t a direct relationship.

Filters flowing between related tables are controlled by CROSSFILTER. It lets you specify how filtering should propagate between two tables, choosing either a single direction or bidirectional flow. This is exactly what defines the cross-filtering direction for a relationship, allowing you to override the default model behavior when you need filters to travel from one side to the other (or both ways) in your calculations.

The other options serve different purposes: PATH builds a path in a parent-child hierarchy, not the filtering direction between two tables; USERELATIONSHIP activates a particular relationship in a measure without changing its inherent direction; TREATAS maps values from one table to another to apply filters when there isn’t a direct relationship.