Forum Discussion
Issue with Input Slicer and Numeric fields in Power BI Service
The issue has been resolved I think. It works fine in Power BI Service now
Hi Farhads,
Thank youj for the follow-up question.
This behaviour currently appears to be related to a known Power BI Service/Input Slicer issue rather than a problem with your report design or data type configuration.
Microsoft has an active tracked issue where the Input Slicer becomes unresponsive after entering values in the Power BI Service, causing filtering problems and degraded behaviour, while Power BI Desktop continues to work correctly. Since your issue only occurs after publishing and numeric fields are not filtering properly, this strongly aligns with the known Service side bug.
As a temporary workaround, Using the Clear icon in the slicer visual header instead of editing/removing entered values manually. Refreshing the report page if the slicer becomes unresponsive. Switching to a standard slicer or Between slicer temporarily until the issue is resolved.
Relevant references:
1. Create and use an input slicer - Power BI | Microsoft Learn
2. Input Slicer Causing Browser Tab Freeze in Public ... - Microsoft Fabric Community
3. Troubleshoot Visualizations in Power BI - Power BI | Microsoft Learn
Hope this helps. If you have any questions regarding this, please feel free to reach out us. We will be happy to help.
Hi v-kpoloju-msft ,
I confirm that this issue is still there so the new feature "Input slicer numeric column support" released with the may 2026 update is completly unusable.
When you use it in Power BI Desktop it works fine, no problem. But as soon as you publish the report in Power BI Service then the Input slicer doesn't recognize the numeric column anymore and treat it as a text column.
Here is an example:
As you can see, in Power BI Desktop I can use the column "VA", which is numeric, with an input slicer and use operator syntax to filter it.
But once the report is published in Power BI Service it get the issue:
The input slicer now treat my "VA" column as text and you can see that I now have the usual text options (Contains all, contains one...) and the Sum of the "VA" displayed in the card is not filtered anymore.
I hope this issue will be solved soon because it was a good addition to the input slicer but unfortunately we can't use it at all.