Issue - Slicer Panel Selections

[Malcolm_S]

In the slicer panel visual, while editing from the visualizations panel; within the "selection" pane, and you click the option to show the "select all", if you then click select all on the slicer that is being edited. Then go back to the selection options and remove the show select all option, the "select all" option will be permantely selected in the slicer panel until an editor goes back and enables the options and deselects it from the slicer. 

I'm not sure if this is by design, but if you overlook this like I did, you'd spend hours trying to figure out why your slicers are filtering inversely. On the otherside, if you are looking to filter inversely you can do this "trick", otherwise I believe PBI should automatically revert to no selections on the slicer panel when this occurs. 

[Anonymous]

Hi  @Malcolm_S 

I tried to restore the scenario you mentioned but failed, can you provide your sample via video or screenshot for reference ? 

How to provide sample data in the Power BI Forum - Microsoft Fabric Community

Best Regards,
Community Support Team _ Ailsa Tao

[Malcolm_S]

@Anonymous Here you go, I just downloaded the sample data from pbi (competitive market analysis). Here are my steps to produce the issue in that dataset: 

1. Created a slicer for the manufacturer.
2. Turned the "select all" option on for the slicer.
3. Selected the "select the all" option on my manufacturer slicer. 
4. Turned off the "select all option" for the slicer. 
5. Then selected a single option in the slicer, In the example I have selected "Abbas".

I know technically, when the background changes on the selection to the color of the slicer, that is the one not "selected". However, while developing a PBI this may not be something you're so much focused on. Especially since, all of the slicer options will be of one color.

For example in my live working scenario, I had created a calculated column as the field for my slicer. Which was a simple if condition, but my options were inversely selecting. I verified my data did not have any wierd duplicates, triple checked my simple dax. Creating a new slicer proved that something was up with the original one. All I'm saying here is it can definitely be debated on whether this proves to be a "real" issue or not. Running into this "issue" in the real-world can take some troubleshooting time though.

 I do think the slicer options can be improved here to have a little more developer friendly approach. Here are my ideas:

• Including an inverse selection option. As I do see people asking questions to do this fairly often. 
• Also maybe logic to prevent the select all option to persist on a slicer after that option is turned off.