Forum Discussion
Weird Slicer Behaviour
I have this kind of a structure and I am trying to have all the categories on a single slicer such that they cascade. I am faced with a confounding issue.
- When I select (say) Planet 1 and Planet 2 on the slicer (multiple select allowed), one of my visuals updates the data. That is fine.
- However, now when I select Solar System 1AS (which has only Planet 1 and Planet 2) the visual updates to include everything else on the data model too. I am expecting it to never update or show anything different from when I select Planet 1 and Planet 2 together.
Hi Nozama
What you're describing sounds like a classic issue with filter propagation in the data model — particularly when relationships between hierarchy levels (e.g., Planet → Solar System → Galaxy → Universe) are not properly configured or behave unexpectedly.
Here are a few troubleshooting steps to consider:
-
Check your relationships: Make sure all relationships are single-directional (from top to bottom of the hierarchy), and that there are no many-to-many relationships unless absolutely necessary.
-
Validate your slicer structure: If your slicer uses a flattened hierarchy or a disconnected table, it's possible that selecting a higher-level item (like a Solar System) inadvertently expands the filter context beyond the expected boundaries.
-
Test using a simplified measure: Create a temporary measure using
ISFILTERED()orSELECTEDVALUE()to detect whether your visuals behave differently based on what's being selected in the slicer.
To provide more targeted help, please share a sample PBIX file that replicates your model structure — with only the relevant columns and no sensitive data — via any public cloud storage (e.g., OneDrive, Google drive...).
If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly
-
1 Reply
Hi Nozama
What you're describing sounds like a classic issue with filter propagation in the data model — particularly when relationships between hierarchy levels (e.g., Planet → Solar System → Galaxy → Universe) are not properly configured or behave unexpectedly.
Here are a few troubleshooting steps to consider:
-
Check your relationships: Make sure all relationships are single-directional (from top to bottom of the hierarchy), and that there are no many-to-many relationships unless absolutely necessary.
-
Validate your slicer structure: If your slicer uses a flattened hierarchy or a disconnected table, it's possible that selecting a higher-level item (like a Solar System) inadvertently expands the filter context beyond the expected boundaries.
-
Test using a simplified measure: Create a temporary measure using
ISFILTERED()orSELECTEDVALUE()to detect whether your visuals behave differently based on what's being selected in the slicer.
To provide more targeted help, please share a sample PBIX file that replicates your model structure — with only the relevant columns and no sensitive data — via any public cloud storage (e.g., OneDrive, Google drive...).
If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly
-