Currently, slicer synchronization works only when both slicers contain identical data. However, there may be use cases where we want to synchronize filters even when the selected data in each slicer is different. The goal is to have a setup where selecting a value in one slicer automatically selects a predefined corresponding value in the other slicer, even if the slicer data sets are not the same.
Proposed Synchronization Approaches:
Option 1: Predefined Value Mapping
Create a predefined mapping between the values in both slicers. When a user selects a value in one slicer, a corresponding predefined value in the other slicer will be selected automatically. This can be achieved through DAX logic or using a supporting table with relationships to drive the selection behavior.
Option 2: Overlapping Slicers with Hidden Layering
Place the two slicers on top of each other, matching their size, dimension, and design. Configure them such that selecting the first item in the top slicer triggers selection of the first item in the bottom slicer (and so on). Set the top slicer’s transparency to 0% so that it hides the slicer underneath, effectively making the user interact with only one slicer visually while syncing both behind the scenes.
on:
Show hierarchy from fabric semantic model in pivot...
Joe_Barry
on:
Get Pro license users list.
on:
Ability to hide/unhide visuals using DAX
on:
Enable Renaming of Measure Labels in Card Visual "...