Forum Discussion
Solved
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 ...
The issue has been resolved I think. It works fine in Power BI Service now
@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).