Forum Discussion
Unexpected Behavior Between Two Related Tables.
- 1 year ago
This usually happens because:
You're only using fields from the Dimension table in the visual (e.g., Name, Category), without any aggregation from the Fact table.
Power BI visuals respect filter context, and if no data from the fact table corresponds to multiple selected dimension values, the visual will appear blank.
Most often, it’s due to the visual relying on the relationship direction, which doesn’t propagate filters both ways
Solution:
Option 1: Include a Field from the Fact Table in the Visual
Option 2: Check for Bi-Directional Filter (if Required)
Option 3: Use TREATAS in a Measure (Advanced)Note:
This is not a bug but expected behavior based on how relationships and filters work.
Ensure your visuals include aggregated data from the fact table, or use DAX to handle filtering intentionally.
Avoid relying solely on dimension values without any context from the fact table.
This usually happens because:
You're only using fields from the Dimension table in the visual (e.g., Name, Category), without any aggregation from the Fact table.
Power BI visuals respect filter context, and if no data from the fact table corresponds to multiple selected dimension values, the visual will appear blank.
Most often, it’s due to the visual relying on the relationship direction, which doesn’t propagate filters both ways
Solution:
Option 1: Include a Field from the Fact Table in the Visual
Option 2: Check for Bi-Directional Filter (if Required)
Option 3: Use TREATAS in a Measure (Advanced)
Note:
This is not a bug but expected behavior based on how relationships and filters work.
Ensure your visuals include aggregated data from the fact table, or use DAX to handle filtering intentionally.
Avoid relying solely on dimension values without any context from the fact table.