Forum Discussion
Slicer Search Not Working When Enabled
I have a slicer in more report as a dropdown and when search is enabled, no results are returned. I checked that the column in a text format and tried creating a new slicer but the issues remains. This occurs both on desktop and service connected by direct query.
This is newer issues I've experienced as it hasn't occured previously.
Hi negbc ,
Can you orovide more information on this in terms of input/output?based on infomration provided, it looks like search issue.
in DirectQuery, the slicer search feature sends the term directly to the data source, making it behave according to that source's collation rules . If your database has a case-sensitive (CS) collation, searching "product" will return zero results if the data is stored as "PRODUCT" or "Product".Please give kudos or mark it as solution once confirmed.
Thanks and Regards,
Praful
3 Replies
Hi negbc ,
Can you orovide more information on this in terms of input/output?based on infomration provided, it looks like search issue.
in DirectQuery, the slicer search feature sends the term directly to the data source, making it behave according to that source's collation rules . If your database has a case-sensitive (CS) collation, searching "product" will return zero results if the data is stored as "PRODUCT" or "Product".Please give kudos or mark it as solution once confirmed.
Thanks and Regards,
Praful
Hello negbc,
Issue: Dropdown slicer search returns no results in DirectQuery.
Cause: Known Power BI limitation/regression with dropdown + search in DirectQuery; not a model issue.
Fix / Workarounds:
- Switch slicer to List (most reliable).
- Use a cleaned column: TRIM(CLEAN('Table'[Column])).
- Consider a dimension table for slicer values.
- Test in Import mode to confirm it’s DirectQuery-related.
References:
Switching to List + cleaned column is usually enough to fix the issue.
Thanks for help, I belive the case sensitivity is the issues.
