Synchronizing filters when slicer data selections differ
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.
Recent ideas
Option to set custom width for gridlines OR fixed outer padding
When designing reports, using the align and distribute evenly options in the format pane are useful, however when designing report pages with fixed bleeds between visuals I have to follow these steps...IolaWhiteley8 hours agoAdvocate IINew2Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell9 hours agoNew MemberNew21Views2likes1CommentOption to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir111 hours agoMicrosoft EmployeeNew47Views11likes1Comment