Cross-Filter Direction One Direction Issue
Exhibit
Refer to the exhibit. The following is a JSON snippet of a Power BI model relationship:
{
"name": "Sales to Customer",
"fromTable": "Sales",
"fromColumn": "CustomerKey",
"toTable": "Customer",
"toColumn": "CustomerKey",
"crossFilteringBehavior": "oneDirection",
"securityFilteringBehavior": "oneDirection"
}You have a Power BI model where the Sales table is filtered by a Customer dimension. Users report that when they filter a measure from the Customer table (e.g., Customer Count), it does not affect the Sales visual. What is the most likely cause?
Quick Answer
The answer is that the cross-filtering direction is set to one direction (Customer to Sales), which prevents a filter on the Customer table from affecting the Sales visual. This is the core of the cross-filter direction one direction issue: when cross-filter behavior is set to oneDirection, filters flow only from the dimension to the fact table, not the reverse. In this scenario, applying a filter on the Customer table (like Customer Count) cannot propagate back to Sales because the relationship is unidirectional. On the Microsoft Power BI Data Analyst PL-300 exam, this tests your understanding of model relationships and filter propagation, often appearing as a trap where candidates assume all filters flow both ways. A common memory tip is to think of a one-way street: if you need a filter from the dimension to affect the fact, the direction must be set to both, or you’ll get a silent breakdown in your measures. Remember: “One direction, one problem; both directions, both tables listen.”
⚠ Common exam trap
Beware of inactive relationships—they are often the culprit when filters don't propagate.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The relationship is inactive
When a relationship is inactive, filters do not propagate between tables by default. In this scenario, filtering a measure from the Customer table does not affect the Sales visual because the relationship is inactive. Active relationships are required for cross-filtering to work. Options B and C would still allow filtering in specific directions, and D is not a standard setting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The relationship is inactive
Why this is correct
The relationship is inactive, so no filtering occurs. This is the most likely cause.
- ✗
The relationship cardinality is many-to-many
Why it's wrong here
Many-to-many cardinality can still allow filtering with proper cross-filtering settings; it doesn't prevent filtering entirely.
- ✗
The cross-filtering direction is set to one direction (Customer -> Sales), but the filter is applied on Customer
Why it's wrong here
One-directional filtering from Customer to Sales would actually allow Customer filters to affect Sales, so this would not cause the issue.
- ✗
The security filtering behavior is set to oneDirection
Why it's wrong here
Security filtering behavior is not typically set to 'oneDirection' and would not prevent filtering from Customer to Sales if the relationship is active.
Go deeper
Related to this question
About these practice questions
This PL-300 question is part of Courseiva's 217-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PL-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You have a data model with a Sales table and a Date table. You create a measure: Total Sales = SUM(Sales[Amount]). When you add a slicer for Date[Year], the measure does not filter correctly. What is the most likely cause?
medium- ✓ A.The relationship is inactive
- B.The Date table is not marked as a date table
- C.The Sales table has no relationship to the Date table
- D.The measure uses SUM instead of SUMX
Why A: The most likely cause is that the relationship between the Sales table and the Date table is inactive. In Power BI, only one active relationship can exist between two tables; any additional relationships must be inactive. A slicer on Date[Year] will only filter through the active relationship. If the active relationship is not the one intended for the measure, the slicer will not affect the measure's result. Using USERELATIONSHIP in the measure or setting the correct relationship as active would resolve this.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.