Report Builder & PowerBI Report Builder Visual

[mmsherer]

Hey all!

At a bit of a loss on this one. I had it working about a month ago and now suddenly it isn't.

I have two setups:

• PowerBI Report: This serves as the shell to house four Report Builder Templates via the Paginated Report Visual. I chose to do this a) from a visual perspective, b) familiarity c) ease of managing permissions through our workspace app.

• Report Builder Reports: Four Report builder templates for people to be able to navigate to the powerbi, choose their client & report and then print a report essentially.

This is the error I am getting:

• An unexpected error occurred

• You have attempted to pass an invalid parameter value from the item(s) you have selected. Please update your selections, or enter the parameter values manually, or contact the report author to update the parameter bindings for the paginated report.

• Timestamp: 2025-11-25T19:04:57.111Z

• Root activity ID: 8e8cc17f-7a8a-4fb4-adee-224e0019b5db

• Session ID: 00002e5cadec4ee9b2f58fcc00eae6aa

• Tenant ID: undefined

• Cluster: https://wabi-canada-central-redirect.analysis.windows.net/

• Report ID: 69b9547c-4f0a-4de7-8a30-998c5ee37475

• Capacity ID: undefined

• ReportViewerVersion: undefined

The PowerBI is connected to the Semantic Model, and the report Builder is connected to the table directly that's used as the fact in the model (it was easier to connect to the table directly because I am new, it didn't require any measures, and I figured they'd be the same anyway. I am feeling like this is the tissue)

Here are the things I've Tried:

• logged in & logged out, closed restarted, all the normal things, same error

• i went back to a previous copy of the report builder I had made connected to the same semantic model, and it still gave the error when using the Paginated Report Visual

• I tried a new report in PowerBI and added the table as an import mode SQL connection, same error

• the only difference I can find between the parameters in the one connected to the SM (the old one I know was working) and the one to the table direct is that the direct allows me to make parameters in PowerQuery, but the SM direct gives me the older Query Designer window

• I tried setting up parameters directly in the SM, and adding those instead to the visual same error.

• The paginated reports run fine on their own in Fabric

Kind of at a loss with this one? It's probably something obvious - so happy for feedback or suggestions!

[v-sgandrathi · Accepted solution]

HI @mmsherer,

Thank you @amitchandak for your response.

Check for mismatches in the type and multi-value settings between Power BI and each paginated report. For example, if a report parameter is set as Integer (or GUID) but the visual sends Text, or if one side supports multiple values and the other does not, this can cause errors. Ensure parameter names and data types match exactly, including case. Confirm the report parameter isn’t hidden or internal only, and avoid using Power Query parameters in the paginated template, as they don’t map the same way from the visual. Try entering a simple literal value from the visual to see if mapping is the issue. Clear your browser cache and check that you’re using the latest Paginated Report Visual. The browser console may provide more detail.

Thankyou.

[mmsherer]

Hey thanks for this - I confirmed all my data types, set it only as single select, checked the names and all that. What really did it was the detail of avoiding using Power Query & attempting to connect to a PowerBI Report. Because I had imported the table directly (at the time I was unsure how to get it from a semantic), I was using Power Query - the reports worked on their own this way, but like you say when put into PowerBI it threw the error.  In case anyone wants it, and is super new like me this was the prompt I used, based on your suggestion to avoid Power Query 🙂

You are an expert in building customized reports using Power BI Report Builder. You frequently work with OneLake Semantic Models, and you're currently training a new employee.

Please walk us through how to create a parameterized report step-by-step. Specifically, cover the following:

1. Creating a dataset from a OneLake Semantic Model

   • The model contains a single table called table.

   • Explain how to connect to the semantic model and bring this table into Report Builder as a dataset.

2. Creating a parameter dataset

   • Show how to build a dataset that provides values for a report parameter (e.g., selecting a field from table to filter on).

   • Clarify any best practices for naming, sorting, or shaping parameter datasets.

3. Setting up the parameter in Report Builder

   • Demonstrate how to create the parameter, configure available values, default values, and map it to the parameter dataset.

4. Connecting everything together

   • Explain how to apply the parameter to the main dataset query.

   • Describe how the parameter works during report execution.

Please provide detailed explanations and reasoning for each step as if you are mentoring a brand-new employee.

[amitchandak]

@mmsherer , Please check these two from Guyinacube for passing parameters between the  report and paginated report 

https://www.youtube.com/watch?v=EZifdFfjTNg

https://www.youtube.com/watch?v=OQKgnJkjJDI