Issues With Input Slicer in the web app

X_Man  thanks for highlighting: 

guys I have also posted the same issue here, also raised a ticket with Microsoft support team and referenced these links, hopefully they can find a quick fix.
here is my post:
Re: Input slicer unable to clear text filters afte... - Microsoft Fabric Community

We have a fix and are working it through deployments, as some in UK / London have noticed the fix was already deployed there. We are looking into the secondary issue about bookmarks set up to Clear All not working with Input Slicer, did you perhaps try to delete and recreate your input slicers while dealing with the issue? Anything else that could have invalidated your bookmark?
Also, please post Issues like this, product regressions, over here Issues - Microsoft Fabric Community
We monitor that forum more closely.

Hello Lodha_Jaydeep ,

Unfortunately this has not lead to a resolution. The problem I am facing is specifically with the Input slicer (not any other type of slicer - as those work, but I am slicing approx. 7000 lines - so not exactly purpose built). 

It is interesting that you say this is well documented, as I was unable to find anything, ergo my post. I would really appreciate any insight into this issue occuring and being resolved specifically with an input slicer.

Kind regards,

Ralphy

Hi PBi community, I am facing the same issue on my end. Neither being able to enter multiple values or neither able to remove the value by clicking on the 'X' icon. It was working as expected until this week. It seems to be a bug in the slicer itself and it is really ennoying after waiting so long to get this functionality available. MS Team, can you please fix this issue quickly ? Thank you for your support.

Hi Ralphy2026 

This behavior is actually tied to an active, service-side rendering bug with the native input/text slicer that Microsoft recently introduced in a cloud deployment, which explains why it was working perfectly for months and still runs fine in your local Desktop file. Since the bug causes the web container to completely ignore multiple selection states and freeze up the dismiss "x" clear action once text values are submitted, you can safely bypass it right now for your users by adding a standard Reset/Clear All Filters button (or an explicit reset bookmark) directly to the page container, or by instructing them to use the native global "Reset to default" circular arrow icon located in the main top toolbar of the Power BI Service interface to instantly break the frozen filter state. Alternatively, if your production environment requires a seamless UI experience while the product group finishes rolling out the backend hotfix across all cloud nodes, you can temporarily convert the visual to a standard dropdown or list slicer with a search bar enabled, which completely circumvents the broken text input container code and restores normal single-click clearing for your users.

https://www.youtube.com/watch?v=BtdTo40-puQ
This video demonstrates how to implement a clean reset mechanism to clear multiple selection values inside your reports instantly, which serves as a highly reliable workaround for users whenever the default visual header clear buttons experience transient service-side bugs.

We still have the issue that removing the input slicer content on one page does not always clear the input slicer on other pages, even though they are synchroniced.

Hi Ralphy2026,

This is a well-documented but frustrating issue with multiple possible root causes. Since it worked fine for 5 months and broke suddenly without you changing anything, this strongly points to one of the service-side causes below. Let's walk through all of them from most likely to least likely.

Most Likely Cause Persistent Filters / Cached Slicer State

Power BI Service saves user slicer and filter choices and reapplies them when users return this can cause the slicer to behave differently per user depending on their cached state. Microsoft Community If your slicer somehow had a single-value state saved into the session, the service locks it into that behaviour.

Fix:

• In the web report, click the Reset to default button (top toolbar, circular arrow icon)
• Or use Reset filters and slicers from the report menu
• Trying to reset filters on the Power BI Service resolved this for several users who experienced the same issue. Microsoft Community

Second Most Likely "Multi-select with Ctrl" Toggled On in Service

A Power BI Service update may have silently toggled on the "Multi-select with Ctrl" setting in your slicer, which means users now need to hold Ctrl to select multiple values and clicking alone only selects one.

Fix in Desktop:

• Open the .pbix in Power BI Desktop
• Select the slicer → Format pane → Slicer Settings → Selection
• Confirm: Single select = OFF, Multi-select with Ctrl = OFF
• Republish to the service

Third Cause Known Button Slicer Bug (if you're using the new Slicer visual)

There was a known bug specifically affecting the Button Slicer (the newer slicer visual introduced in 2023) where multi-select would stop working after publishing selected items would deselect when a second item was chosen in the web app. Microsoft Fabric Community Microsoft acknowledged and resolved this, but it may recur after service updates.

Fix:

• Ctrl + click as a temporary workaround to select multiple items
• If you're on the new Button Slicer, try switching back to the classic List Slicer temporarily to confirm this is the cause
• Republish after the latest Desktop update

Fourth Cause Bookmarks Overriding Slicer State

If your report uses bookmarks, they can capture and forcibly restore a slicer's selection mode overriding your intended multi-select behaviour every time a bookmark is triggered. Microsoft Fabric Community

Fix:

• Go to View → Bookmarks in Desktop
• For each bookmark, right-click → Update after setting the slicer correctly
• Make sure "Data" is unchecked in bookmark capture if you don't want it to override filter states

Fifth Cause "X" to Remove Selection Not Working

The X button to clear a selection not appearing or not responding in the web app is specifically tied to the Visual Container Header being disabled.

For the new Slicer visuals, the Clear button was moved into the Visual container header — if the report author disables the Visual container header, the Clear button isn't available. Microsoft Learn

Fix:

• In Desktop: Select the slicer → Format pane → General → Visual container header → toggle On
• Republish

Step-by-Step Resolution Order

Try Step 1 first it resolves this for most people. If it persists after Step 4, it's likely a service-side regression and worth submitting via Help → Report a problem in Power BI Service.

Hope this fixes it!

I just experience it is working well in Edge environment, but not in Chrome environment...

This seems to have rectified itself without any action from my side. Quite an annoying occurance, but glad it is not affecting me anymore. Leaving this unanswered as I can see there are some very recent occurances of this issue on other people's systems - and that deserves attention. 

Additionally to the topics above we encountered another issue:

If we clean the input slicer (e.g. via rubber, as the X is not always working), the cleaning is not always taken over to other pages that have the same synchronized input slicer.

The issue only exists on the server version. On Power BI Desktop it works without issues.