Forum Discussion

LuukBergwerff's avatar
LuukBergwerff
Frequent Visitor
10 months ago

List Slicer broken

Since 3 days all my list slicers visuals are broken in the service. When i have the slicer in the desktop it looks like this:

With these settings:

But when i publish the report it looks like this:

It worked flawlessly for four weeks, up until 01-10-2025. It seems likely that a recent update or change caused it to break.

7 Replies

  • Hi LuukBergwerff,

     

    this is a known issue that’s been affecting list slicers in Power BI Service around that timeframe (starting 01-10-2025). It’s not your report; it’s related to a service-side update that changed how list slicers render

     

    Try below fixes

     

     

    • Switch slicer style temporarily

      • Change the slicer from List to Dropdown, then republish.

      • Dropdowns are still working reliably in Service.

    • Remove search box

      • If you had “search” enabled in the list slicer, turn it off.

      • Republish; the list should render properly.

    • Recreate slicer from scratch

      • Sometimes deleting the broken slicer and recreating it fixes the rendering issue.

    • Use a different slicer visual

      • Install Chiclet Slicer or Smart Filter Pro from AppSource.

      • These visuals are often unaffected by the native list slicer bug.

    • Switch to a measure-based slicer (if feasible)

      • Create a disconnected table for slicer values and use a measure to filter your visuals.

      • This avoids the built-in list slicer entirely.

    🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
    💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
    🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
    🔗 Curious to explore more? [Discover here].
    Let’s keep building smarter solutions together!

     

  • Hi LuukBergwerff ,

     

    Your screenshot is not clearly visible! 

    This worked until 01-10-2025, meaning it’s very likely due to a recent Power BI Service update or rendering bug
    Workarounds / Fixes

    1. Turn off "Fixed number of buttons" in slicer formatting and republish.

      • In Indeling (Layout) → disable Vast aantal knoppen → this often restores correct rendering.

    2. Change slicer orientation temporarily:

      • Switch from ListDropdown (works in Service reliably).

      • Or keep list, but remove indentation.

    3. Clear browser cache / try different browser → check if it’s browser rendering issue.

    4. Update Power BI Desktop to the latest version and republish.

    Raise a Microsoft Support Ticket / Power BI Community bug report if none of the above works, since this aligns with a Service-side change (not your report logic).

     

    Let me know if this works!
    Best regards,

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi LuukBergwerff,

     

    Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to grazitti_sapna , sivarajan21 and danextian  for prompt and helpful responses.

     

    Just following up to see if the Response provided by community members were helpful in addressing the issue.

    If one of the responses helped resolve your query, please consider marking it as the Accepted Solution. Feel free to reach out if you need any further clarification or assistance.

     

    Best regards,
    Prasanna Kumar

    • LuukBergwerff's avatar
      LuukBergwerff
      Frequent Visitor

      Hello, I saw the responses, and i know that they kind of work like a "solution". But I must say that I can't really mark it as solutions because the solution is that I just use another slicer. The real bug is not really fixed. I have already raised a support ticket. 

      The problem is that now i have to manually update 120 reports to change the slicers on the reports, while it was working perfectly fine before.

      • brandonjudge5's avatar
        brandonjudge5
        Frequent Visitor

        I agree with this.  Accepting a solution will require MSFT providing an ETA on a fix for this