Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago

Suggestions For Getting Slicers To Work

I have two slicer controls, a multiselect (Fuel) and single select (Model).

 

If I select a value from the Model slicer, then deselect a value from the Fuel slicer that contains the selected value from the Model slicer, this value remains selected (even though it should now be removed). When I then select another value from the Model slicer, the rogue value gets removed.

 

I have created a very simple pbx file so you can see this problem. To replicate, ensure you have 'Mustang Mach-E' selected, then deselect the 'Electric' option from the Fuel slicer.

 

Note that even if I use bi-directional filtering betweens the tables, you can still replicate this issue.

 

Does anyone have any suggestions to fix this (apart from Bookmarks which are not possible for my solution)?

6 Replies

  • Seanan's avatar
    Seanan
    Solution Supplier

    Hi Anonymous 

    I believe I have fixed the issue by deleting the current model slicer, copying and pasting the fuel slicer and then changing the value to the model column. This does include the "Select all" option, is this a problem?

    Please find the PBIX file for testing here.

     

    Kind regards,
    Seanan
    If this post helped, please consider accepting it as the solution.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thanks for this. However, the second slicer needs to be a single-select, and when I change it back to single, I'm still able to deselect Electric when Mustang Mach-E selected (thus the problem still remains).

       

      • Seanan's avatar
        Seanan
        Solution Supplier

        Hi Anonymous 

        Apologies, I've done some digging around and it seems like a lot of users have run into this issue and have not been able to find a solution.

        You can post this as an idea at: https://ideas.powerbi.com/ideas/

  • Anonymous's avatar
    Anonymous
    Not applicable

    I've create a new idea to either fix this or allow default values to be programmatically selected.