Forum Discussion
Unable to render paginated report - One or more parameters required to run the report have not been
- Anonymous6 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.
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
hi Craig and Nick,
We have identified an issue with using hidden parameters. This scenario regressed with most recent deployment and we are working on fixing the issue. For your scenarios, did you pass the hidden parameter through URL from web appt to the embedded paginated report? Please do file a support case to ensure timely communication regarding the fix.
Thanks,
Rohit
- Anonymous6 years agoNot applicable
Hi rpatkar,
Yes, we are passing the hidden parameter value via URL.
I filed a support case for this yesterday (#120092124008667). The agent I spoke to followed up overnight to say that he had escalated the issue to the backend engineering team.
Thanks,
Craig- Anonymous6 years agoNot applicable
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.
- Anonymous6 years agoNot applicable
Is anyone aware if this fix went into Production? If so, must users recreate their subscriptions now? We are still receiving error messages on our old/existing subscriptions.