Forum Discussion
Input Slicer Filtering Rule Stops Working After Publishing to Report Server
Hi everyone,
I have a question regarding the "Input slicer" visual in Power BI.
I created an input slicer in Power BI Desktop and set the filtering rule to "Does not contain any". It worked perfectly in Desktop during my local tests, filtering data as expected.
However, after publishing this report to our on-premises Power BI Report Server, the input slicer's behavior seems to have changed:
The operator dropdown button is missing: The dropdown button that allows me to switch between operators (e.g., "contains", "does not contain") in Desktop is no longer visible on the server.
Filtering logic appears different: When I enter a value, it seems to apply an exact match logic instead. Only when I type the complete and exact value can it filter the data. The "does not contain any" rule I originally set no longer seems to work.
Has anyone else encountered this issue? What could be the possible causes? Is this due to limited support for the input slicer visual in certain Report Server versions, or could it be that I missed some important step before publishing?
Just to add more details to this issue: I recently upgraded our Power BI Report Server from the September 2025 version to the May 2026 version (version 15.0.1121.120)
I'd really appreciate any insights or suggestions!
Thanks in advance.
Hi Simonawu ,
Thank you for reaching out to Microsoft Fabric Community Forum,Below are the few points which can resolve your issue.Let us know if you need any further assistance.
- The issue is most likely related to Power BI Report Server feature compatibility, rather than an incorrect slicer configuration.
- The Input Slicer supports operators such as “Contains” and “Does not contain any” in Power BI Desktop/Service, but PBIRS may not have full feature parity.
- Since the operator dropdown is visible and works in Desktop but disappears after publishing to PBIRS, this points to a PBIRS rendering/runtime limitation or bug.
- You upgraded from September 2025 PBIRS to May 2026 (15.0.1121.120), so the PBIRS version should be specifically considered.
- Verify that the PBIX was created/edited using the Power BI Desktop for Report Server – May 2026, matching the PBIRS version.
- Create a simple test PBIX with an Input Slicer and test “Does not contain any”. If it works in Desktop but not PBIRS, the issue is isolated to PBIRS.
- Do not change the DAX or data model yet; the disappearing operator indicates that the problem is likely with visual support in PBIRS.
- Check the May 2026 PBIRS release notes for known Input Slicer/slicer issues.
- If the behavior persists with the matching Desktop version, raise a Microsoft support ticket and provide:
- PBIRS version
- Power BI Desktop for Report Server version
- PBIX file
- Screenshot showing the operator in Desktop
- Screenshot showing the missing operator in PBIRS
Thanks,
Chaithanya.
3 Replies
Hi Simonawu ,
Thank you for reaching out to Microsoft Fabric Community Forum,Below are the few points which can resolve your issue.Let us know if you need any further assistance.
- The issue is most likely related to Power BI Report Server feature compatibility, rather than an incorrect slicer configuration.
- The Input Slicer supports operators such as “Contains” and “Does not contain any” in Power BI Desktop/Service, but PBIRS may not have full feature parity.
- Since the operator dropdown is visible and works in Desktop but disappears after publishing to PBIRS, this points to a PBIRS rendering/runtime limitation or bug.
- You upgraded from September 2025 PBIRS to May 2026 (15.0.1121.120), so the PBIRS version should be specifically considered.
- Verify that the PBIX was created/edited using the Power BI Desktop for Report Server – May 2026, matching the PBIRS version.
- Create a simple test PBIX with an Input Slicer and test “Does not contain any”. If it works in Desktop but not PBIRS, the issue is isolated to PBIRS.
- Do not change the DAX or data model yet; the disappearing operator indicates that the problem is likely with visual support in PBIRS.
- Check the May 2026 PBIRS release notes for known Input Slicer/slicer issues.
- If the behavior persists with the matching Desktop version, raise a Microsoft support ticket and provide:
- PBIRS version
- Power BI Desktop for Report Server version
- PBIX file
- Screenshot showing the operator in Desktop
- Screenshot showing the missing operator in PBIRS
Thanks,
Chaithanya.
Hi Simonawu ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
Hi Simonawu ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya