Forum Discussion

AvPowerBI's avatar
AvPowerBI
Icon for Post Patron rankPost Patron
6 years ago
Solved

Unable to render paginated report - One or more parameters required to run the report have not been

Hi,   We have a number of rdl reports uploaded to the Power BI Service, we've had no issues with these reports and have been running fine for month but today for some reason we are getting the belo...
Need Help
  • Anonymous's avatar
    Anonymous
    6 years ago

    FYI ... Today, MS Support confirmed this issue and informed me that a fix in in the works:

    • Issue Definition: RDL reports with hidden parameters fails to render with Error as "Unable to render paginated report One or more parameters required to run the report have not been specified".
    • Resolution: Backend team did the investigation and confirmed that they have identified the issue and currently they are working on a fix which is expected to be deployed by 10/2/2020.
Anonymous's avatar
Anonymous
Not applicable
6 years ago

Same issue manifested for me today. Was this ever resolved and explained?

Thanks,

Craig

  • rpatkar's avatar
    rpatkar
    Icon for Power BI Team rankPower BI Team
    6 years ago

    hi Craig,

     

    Please provide the request Id from error dialog and answers to the 3 questions I posted above. This will help me investigate better. Thanks!

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Thanks rpatkar 

      Here is an example of the error:

      Unable to render paginated report
      One or more parameters required to run the report have not been specified.
      Activity ID: 21623694-c49a-4490-5377-323470e8f835
      Request ID: 21623694-c49a-4490-5377-323470e8f835
      Correlation ID: 488b03d4f1254b02972338b0d5ef80b6
      Status code: 200
      Time: Mon Sep 21 2020 09:43:31 GMT-0400 (Eastern Daylight Time)
      Cluster URI: https://canadacentral.pbidedicated.windows.net/webapi/capacities/356362E6-A553-4E04-852D-8034A69784C5/workloads/RsRdlEngine/rs/automatic/v1.0

      As for the questions ... 

      1. No, I have not opened a support ticket yet. Thought I'd check on this thread first to see if there was a DIY resolution.
      2. It's a bit complicated and ties in with Q3.-- see explanation below.
      3. Yes, the report uses a hidden parameter to control data security (RLS).

      Explantions for #2 & 3:

      • The report is embedded in a web app (app owns data) which is where the error message appears. The embedding app passes a value to the hidden parameter to restrict the data displayed (RLS).
      • The report renders without error when opened in Report Builder, and in the Power BI Service only if the hidden parameter is unhidden (report is not usable in Power BI Service otherwise because it doesn't have the hidden parameter value there).
      • The data source is an Azure SQL database in the same subscription/tenant. No gateway needed.

      No changes were made to the report or data source. Users started reporting the error early this morning (EDT).

      If there is no simple resolution, I can log this same information to a support ticket.

      Thanks,
      Craig

       

      • Anonymous's avatar
        Anonymous
        Not applicable
        6 years ago

        We have the same problem. It all started today and has pretty much the same approach to paginated reports and RLS. I have oppened a support ticket but no answer yet. I'll let you now if i get any solution for the problem. 

        /Nick