Forum Discussion
Issue with Input Slicer and Numeric fields in Power BI Service
Looks like there is a bug in Power BI service only, where numeric fields are treated as text fields and cannot be filtered properly when using the Input Slicer and a numeric field. This only happens when a report is published to the power bi service - no issues with Power BI Desktop. Even in the text mode it doesn't filter values.
The issue has been resolved I think. It works fine in Power BI Service now
14 Replies
@Farhads has described the issue well and I have the exact same issue. The Input Slicer, when configured to a numeric input, works properly in the Power BI app but once the report is published, the Input Slicer is non-functional. The UI in the published report behaves as if it were a text field and shows the filter operator button (which isn't even able to be configured in the visualization settings when you choose a numeric input so clearly something is broken on Microsoft's side).
I think these issues are not related (though I could be wrong). The issue I described happens ONLY to numeric columns and there are no issues with Input Slicer responsiveness - it is responsive and works well with the text fields. The issue is it doesn't recognize numeric fields as such. In the example below, I'm taking a numeric column MonthOnBook , you can clearly see it is a numeric column in the standard slicer as it works as a Between slicer. However, the Input slicer is showing all the options related to text fields i.e. Contains Any, Starts with any etc. whilst in Power BI desktop these options do not appear as they are not relevant to numeric columns.
Hi Farhads,
Thank you for the clarification and screenshots and also thanks to Akad for his response for the above question.The MonthOnBook field is correctly recognized as a numeric column in Power BI Desktop and in the standard slicer (Between slicer works as expected). However, after publishing to Power BI Service, the Input Slicer incorrectly treats the numeric field as text and shows text-based operators such as Contains any and Starts with any.
This behaviour is now much more likely to be a Power BI Service-side issue/regression rather than an expected limitation, because the official Microsoft documentation confirms that the Input Slicer supports both text and numeric data columns.
Create and use an input slicer - Power BI | Microsoft LearnHope this helps. If you have any questions regarding this, please feel free to reach out us. We will be happy to help.
Hi Farhads,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.
Hi Farhads , Can you explain the issue with a sample data to understand it clearly ? did you check id you have turned off the edit interactions ?
Thanks!
Natarajan Manivasagan
If you found this helpful, please consider giving it a Kudos and marking it as the accepted solution — it goes a long way in helping others facing the same issue.🏆 Best Solution for Enterprise BI — 2026 Microsoft Fabric Semantic Link Developer Experience Challenge
👉 Microsoft announcement · View the winning notebookFor more Power BI tips and discussions, let's connect on LinkedIn.
Cheers!
Hi Natarajan_M
I created a brand new report in Power BI desktop. New table (table1) with a numeric column (Column1) . I used Input Slicer and added Column1 to it. Everything works fine in Power BI Desktop. When I publish the same report to power bi service the filter stops working. From what I see the Input Slicer doesn't recognize Column1 as a numeric column and instead is behaving like a filter for text columns i.e. showing : Contains Any, Starting With etc options. The problem is clearly in power bi service as I don't have any issues with Power BI Desktop.
Hi Farhads : can you republish it as a new report and check
if possible can you place it in a one drive and share it here
ThanksHi Farhads.,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to redkardz, Natarajan_M, for those inputs on this thread.Has your issue been resolved? If the response provided by the community member redkardz, Natarajan_M, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.hi v-kpoloju-msft No, the issue is not resolved - this is clearly a bug in power bi service ( I assume in some regions only) or the new feature (Input slicer numeric column support (Generally Available)) has not been rolled out to all regions yet.
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.
