Slicer "Select all" on mobile view does not work in all configurations

[paulmmorgan]

"Using a Slicer in Dropdown configuration and am experiencing issues on mobile view only, when implementing "Select All" (and Search)

1. If Search is enabled then the "Select All" function does not work; the current state of "select all" remains unchanged (so unchecking Select all when all items are selected does not uncheck all items, they remain selected)

2. "Select all" may not work when "Search" is turned off either - but it's very random to understand how this bug surfaces

The only way I have found to fix this issue is to delete the control and rebuild it, along with configuring the mobile view. 

[Anonymous]

Hi @paulmmorgan 

I tried to restore the scene you said, but failed. Can you show your issue through video or screenshots ? 

Best Regards,
Community Support Team _ Ailsa Tao

[JD07122022]

Experiencing the same issue on IOS app. Select all can not be unselected in mobile app in vertical view. If I switch to horizontal view (to have similar outfit as web) it can be unselected.

[paulmmorgan]

This has to be enabled as a mobile view experience, not web

You need to enable search in the slicer

You enable "select all" 

that combination of setting will cause the issue

[JD07122022]

Hi @paulmmorgan 

good to hear you solved it! Can you elaborate:

I tried following options (A-D) and all were unsuccessfull, do you suggest one of those or another combination?

So far I couldn't solve it, select all is simply not possible on the mobile optimized view. 

A

Search enabled

Select all enabled (web)

B 

Search disabled

Select all enabled (web)

C

Search enabled

Select all enabled (mobile only)

D

Search disabled

Select all enabled (mobile only)

[Anonymous]

Hi @paulmmorgan 

I am so glad to hear that your issue has been fixed . Thanks for your sharing . 

Best Regards,
Community Support Team _ Ailsa Tao

[JD07122022]

Hi @Anonymous 

I still do believe it is an actual PBI bug. I rebuild the control and all options see above lead still to the bug.

Haven't found any combination that solved it so far.

[paulmmorgan]

@Anonymous I never said it was fixed; it's still a bug - I was qualifying how I could recreate the issue