Force Selection in new slicer does not work

[Thomas87]

Hi all,

It appears that the force slection feature in the new slicer is not working as expected. I have two slicers A & B. Slicer A affects the available options in slicer B. Assume I have something sleected in Slicer B and now I sleect a different value in slicer A. Due to the interaction from slicer A on the possible values in B the value that was selected is no longer available, however even though force sleection is switched on, slicer B does not pick an availble option in the list.

I know that for example the custom chiclet slicer visual does support this behaviour but the chiclet is limited in terms of styling and slightly buggy so ideally i want to replace it by the new slicer. however, as long as the force sleection is not functioning properly i can't. Please solve this bug.

[Alex87]

You can write directly on linkedin on "PBI core visual" channel, to Miguel Myers (who is very open to feedback), explaining your use case and the added value it could bring. I already heard Miguel talking about this feedback but did not retain the expected date of implementation.

[Alex87 · Accepted solution]

Hello Thomas,

The force selection feature in the new filter visual is a bit confusing. The behavior is the one below.

This being said, Miguel Myers is aware of this limitation you describe and I think this feature is in the roadmap. Hopefully, we will no longer have phantom selections !

New button slicer | LinkedIn

[Thomas87]

Hi Alex, thanks for your response! That does explain the problem.... my expectations! 🙂 Hopefully the 'force selection' feature as I described it will be picked up quickly seeing as it is a requirement for our use-case. Any idea if there is a way to influence or vote on backlog items like these?