Forum Discussion

mustafa_data's avatar
mustafa_data
Frequent Visitor
1 month ago
Solved

Power BI Input Slicer Issue on Web

Dear Team,

I am using the Power BI Input Slicer with the Accept Multiple Values option enabled. I am currently using the April 2026 version of Power BI.

The feature works correctly when I paste a single barcode in both Power BI Desktop and the Power BI Service (Web).

However, the issue occurs when a user pastes multiple barcodes in the Power BI Service. Instead of recognizing each barcode as a separate value, the web version treats the entire pasted content as a single string.

For example, when I paste multiple barcodes:

Power BI Desktop:

XXXXX
XXXXX
XXXXX

Each barcode is recognized as a separate value, and the visual filters correctly.

Power BI Service (Web):

XXXXX XXXXX XXXXX

The entire input is treated as one string, so the filter does not work.

The exact same list of barcodes is being copied and pasted in both Desktop and the Web, but the behavior is different.

Could you please let me know if this is a known issue or if there is a solution or workaround?

Thank you.

16 Replies

  • Hii mustafa_data 

     

    Update Power BI Desktop, republish, and test in another browser. As a workaround, use the List slicer, which officially supports pasting one value per line, or enter each barcode separately and press Enter to create individual filter pills. If it persists, raise a support ticket with the PBIX, browser version and Service version.

    • mustafa_data's avatar
      mustafa_data
      Frequent Visitor

      Hi rohit1991  Thanks for your reply.

       

      When user paste one by one barcode it working... but users used to have multiple barcodes, they just want to through barcodes either 5,10 or 100 and see the results. 

  • mustafa_data  This is a known behavior. Set the slicer's delimiter to space (or comma) instead of relying on line breaks, and standardize how users copy the list. Because barcodes don't contain spaces, a space delimiter will make Desktop and Service behave identically.

     

     

    • mustafa_data's avatar
      mustafa_data
      Frequent Visitor

      Hi Tahreem24  Thank you for the response, but Set the slicer's delimiter to space (or comma) instead of relying on line breaks < How I can set this?

  • Hi,

    That confirms it's the paste-parsing itself, since one-by-one works fine, the filter logic is fine, it's specifically bulk multiline paste that's getting flattened on Web.

    Since users need to paste 5-100 barcodes at once, here's what I'd try:

    Ask users to paste as plain text (Ctrl+Shift+V) instead of a normal paste, worth testing if that preserves line breaks on Web.

    Test in a different browser, if Chrome vs Edge behaves differently, that tells you it's a browser clipboard issue, not the visual itself.

     

    💡 Helpful? Give a Kudos 👍 — keep the community growing.

    Solved your issue? Mark this as the Accepted Solution ✔️

    Best regards,
    Prince Singh | Data Science & Microsoft Fabric Enthusiast

      • Prince0011's avatar
        Prince0011
        Solution Sage

        Hi,

        That setting is under Format visual > Values (or sometimes just labeled Input settings depending on your version), there should be a delimiter option there where you can pick space, comma, or line break as the separator.

        Once that's set to space, users can paste their barcode list separated by spaces instead of line breaks, and since Desktop and Web both handle spaces consistently (it's specifically line breaks getting flattened on Web), that should make both platforms behave the same.

        If you don't see a delimiter setting in Format visual, check under the visual's own icon/gear settings when you click into it directly on the canvas, some of these input-style settings live outside the standard Format pane depending on the version you're on.

  • This looks like a difference in how the visual's underlying input control handles pasted line breaks in a browser versus the Power BI Desktop webview. A plain single-line HTML text input collapses newlines into spaces on paste, which matches exactly what you're seeing in the Service. A couple of things worth checking: 1) Confirm the visual version is identical in Desktop and the Service - organizational visual stores can cache an older version of a custom visual, which can cause exactly this kind of inconsistency. 2) Try pasting with a different delimiter (comma or semicolon instead of line breaks) if the visual supports it, since those often survive paste-into-input-field better than newlines. If the version matches and the behavior persists, this looks like a bug in the visual itself rather than a Power BI platform limitation - worth reporting it to the visual's publisher through its AppSource support link with this exact repro.

    • mustafa_data's avatar
      mustafa_data
      Frequent Visitor

      Hi Divyaraj_Rathod  Thank you for your reply.

       

      1. The first Power BI version I had of April 2026, I updated today and Installed July 2026, now the same functionality not working on Desktop as well.

      2. It's build in slicer coming from Microsoft. 

      3. I tried by comma separation but still not working. 

      • Divyaraj_Rathod's avatar
        Divyaraj_Rathod
        Helper II

        Hi mustafa_data, thanks for confirming those details - that changes things. Since this is the native Power BI slicer (not a custom visual) and the paste-multiple-values issue now reproduces on Desktop too after updating to July 2026, this looks like a regression introduced in that build rather than a browser/webview difference.

         

        A few things worth trying: 1) Note the exact build numbers via Help > About for both the April and July installs. 2) If you still have the April 2026 installer, test it side by side to confirm the regression. 3) As a workaround, try typing values one by one with Enter instead of pasting, or paste into Notepad first then copy from there into the slicer, which sometimes avoids rich-clipboard parsing issues. 4) Since this is a core product bug affecting the built-in slicer, report it directly via Help > Submit a feedback > Report a problem with your repro steps and both build numbers - that's the fastest path to an actual fix, since community volunteers can't patch core product bugs. Also worth checking the July 2026 Desktop release notes/known issues in case this is already tracked.