Forum Discussion
Paginated Reports Back Navigation Fails When Multi-Value Parameter Uses Select All
What’s happening is that Select All is not stored as the full explicit list of values. When you navigate to the subreport and then use the Back button, Report Builder tries to re-validate the parameter using a stale or incomplete value set, which causes the validation error. When you manually select values, the parameter contains an explicit list, so validation succeeds.
Practical workarounds:.
Use a custom “All” value (e.g. -1) and handle it in the dataset query instead of the built-in Select All.
Convert the parameter logic to explicitly expand “All” into all values in the dataset.
WHERE
(
@MyParam = '-1'
OR MyColumn IN (@MyParam)
)
Hi cengizhanarslan ,
This report has been working correctly for the past two years.
Has there been any recent update or change on the Power BI Service side that could have caused this issue?The solution you mentioned would require changes at the individual report/dataset level.
Could you please suggest an alternative solution that does not require modifying each report?Hi Nagaraj_D ,
Thanks for the clarification.
There has been no publicly documented or announced change in the Power BI Service specific to paginated reports that explains this behavior. That said, service side updates are rolled out regularly, and changes can affect how parameter state is restored during navigation, even if the report definition itself has not changed. This would also explain why the report worked for a long time and started failing without any updates to the report.
At the moment, there is no tenant level or global setting that can change how the built in Back button handles Select All for multi value parameters. That logic is handled by the service and cannot be overridden centrally. As a result, avoiding report level changes limits the available options.
If modifying individual reports is not feasible, the only alternatives are to avoid relying on the Back button for navigation or to raise a Microsoft support ticket so this can be validated as a service side issue or regression. A support case is also the best way to confirm whether a fix can be applied without changes at the report level.
If you do open a support ticket and receive an update, sharing the outcome here would be helpful for others facing the same behavior.
Please reach out for further assistance.
Thank you.Hi Nagaraj_D ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.Additionally, could you please confirm whether the issue has been addressed through the support ticket with Microsoft?
If the issue is now resolved, we’d greatly appreciate it if you could share any key insights or the resolution here for the benefit of the wider community.
Thank you.
