Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
We are experiencing an issue with Text Input Slicers in Power BI Service where the slicer value does not reset when using bookmarks or the Clear All Slicers option.
A user types a value into a Text Input Slicer (e.g., MRN).
Clicking a Reset/Clear bookmark visually clears the slicer.
When the user interacts with the slicer again, the previously typed value automatically reappears.
This behavior occurs only in Power BI Service.
The same report works correctly in Power BI Desktop.
Text Input Slicer values should fully reset when a reset bookmark or Clear All action is applied.
After reset, the slicer should not retain or reapply previously typed values.
This issue affects all reports using text-based slicers (e.g., MRN, Account Number).
Dropdown slicers work as expected and reset correctly.
This behavior appears to have started after a recent Microsoft Fabric / Power BI Service update.
The issue is not related to report design, bookmark configuration, or persistent filter settings.
Prevents reliable Reset Filters functionality.
Causes user confusion when old values reappear.
Forces redesign of production reports to avoid text input slicers.
Replace Text Input Slicers with Dropdown slicers, which reset correctly.
Could someone from the Power BI / Fabric product team please confirm whether this behavior is by design or a known issue planned to be addressed?
This impacts multiple production reports and is forcing us to replace text input slicers with dropdowns.
Understanding whether a fix or configuration option is planned would help us decide whether to wait for a resolution or permanently redesign our reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sounds like the issue was transient, glad things are working again for your scenario.