Syncing Hierarchical Date Slicers Not Working

Hi WishAskedSooner ,

You’re running into a known Power BI limitation: hierarchical date slicers only propagate filters through active relationships. As soon as you use a hierarchy (like Year > Quarter > Month > Day), the filter doesn’t sync to tables connected via an inactive relationship, even if you’re using USERELATIONSHIP in your measures.

A regular date slicer (single-column) applies a filter directly, so you can sync it across fact tables (using USERELATIONSHIP as needed). A hierarchical slicer sends multi-level filters that only traverse the active path in the model. Fact Table B, relying on an inactive relationship, won’t sync.

Workarounds:

1. Measures with USERELATIONSHIP: For Fact Table B visuals, always use DAX like CALCULATE([Your Measure], USERELATIONSHIP(FactB[Date], DimDate[Date]))
   
   

2. Disconnected Date Table: Advanced but possible, use a disconnected Date table as the slicer, and tie both fact tables’ visuals to it using DAX (with TREATAS or similar). It gives you more control but requires more complex measures and careful model design.
   
   

3. Keep Slicers Non-hierarchical: If syncing is more important than hierarchy, using a regular (single-column) slicer works across both tables, as you noticed.

Make sure both Fact Tables are linked to the same DimDate. “Sync Slicers” in Power BI helps keep slicer visuals aligned across pages, but won’t bypass this hierarchy limitation. There isn’t a built-in Power BI feature that allows hierarchical slicers to sync through inactive relationships (as of July 2025).

Right now, the only robust native workaround is to use standard slicers for full sync or use USERELATIONSHIP-wrapped measures for visuals filtered by inactive relationships. If you ever need a more “hacky” workaround, you could experiment with disconnected slicers and custom DAX, but that can get tricky.