Dropdown slicer silently ignores typing input (search removed without discoverability)

[luke_riley]

Summary

As of Power BI Desktop March 2026 (v2.152.x), dropdown slicers visually accept keyboard input but no longer perform any filtering. Typing is silently ignored with no error, toggle, or UI indication. This behavior previously worked and appears to have been removed without notice.

Description

Dropdown slicers still present a visual affordance that suggests typing will filter values (cursor focus, keystroke acceptance), but no filtering occurs.
This creates a false affordance: the control appears interactive, but user input has no effect.
The only way to enable search is to change the slicer style to List and enable Header → Search. There is no in‑product guidance indicating that search is now List‑only, and no indication in the dropdown slicer UI that typing is unsupported.
This behavior disproportionately impacts enterprise datasets with high‑cardinality fields such as Work Item IDs, Ticket Numbers, or Account IDs, where dropdown slicers were historically usable via typing.

Steps to Reproduce

1. Open Power BI Desktop March 2026 (v2.152.x)
2. Add a slicer visual
3. Set Style = Dropdown
4. Bind the slicer to a text field (e.g., formatted Work Item ID)
5. Click the dropdown and type any characters

Result:

No filtering occurs. Typed input is ignored.

Expected Behavior

One of the following:

• Typing filters dropdown slicer values (previous behavior), or
• Dropdown slicer disables text input entirely, or
• UI guidance indicates that search is supported only in List slicers

Actual Behavior

• Keystrokes are accepted visually
• No filtering occurs
• No warning, tooltip, or setting explains the behavior

Impact

• Significant analyst time wasted troubleshooting data types, sorting, and slicer configuration
• Erosion of trust in Power BI UI consistency
• Repeated rediscovery of the same regression across teams
• Increased support burden in large enterprise environments

Suggested Fix

• Restore typing‑to‑filter behavior for dropdown slicers, or
• Remove the typing affordance from dropdown slicers, or
• Add explicit UI messaging (e.g., “Search available only in List slicers”)

Classification

UX regression / breaking change without discoverability

Final Thoughts

If this behavior is intentional, could the dropdown slicer disable keyboard input or surface guidance that search is List‑only?