Forum Discussion
Weird Slicer Behaviour
- 1 year ago
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
-
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