Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
There are no NULL values in the dataset returned by the stored procedure. What is the problem?
Also, why isn't there a separate Forum for Power BI Report Builder?
How about a decent tutorial that can help walk someone who uses Power BI Desktop every day to learn how to use Power BI Report Builder?
Hey @duncfair , I wish there was a separate forum or section for paginated reports but I try to work around it. As for your issue, without looking at your storeproc code, it's hard to tell. What executes perfectly in SSMS doesn't always execute the same way over on Report Builder side. If it's you who wrote the code, can you please share it? If you can't, then can you run a query profiler on your end? Usually issues like these have to do with how you setup your columns in SQL, specifically data type mismatch like trying to convert a null value into an int, etc. Hope that helps to some degree.
It is a simple stored procedure that uses a text value parameter to return a row of data. The parameter matches on a varchar datatype column in the table, and is defined as varchar within the stored procedure and as text in the Report Builder. Also, there is no query profiler that I can find within Power BI Report Builder (am I missing something?).
The query\stored procedure works fine and returns data as intended when I am in the design mode, but I immediately get the error above when I go to 'run' mode.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 59 | |
| 43 | |
| 42 | |
| 23 | |
| 17 |
| User | Count |
|---|---|
| 190 | |
| 122 | |
| 96 | |
| 66 | |
| 46 |