Forum Discussion
Paginated Report - Parameters stop refreshing after returning from linked reports
Hi,
I've recently been porting my old SSRS reports to Power BI paginated reports, and one of my report links out to a seperate detail report, passing parameters like Report Year, Report Name, Manager and User. This works correctly, however, because all of my parameters are cascading, the dropdowns stop refreshing and I can't choose new parameters. (For instance, 'Report Year' is used in the 'Report Name' query, etc.) Trying to select a different manager does not change the other dropdowns, and gives an error when anything is selected.
Is this a behavior that can be changed, or is there a way to set up how the back button functions? I'm guessing this is not intented behavior, but I might be missing something.
Thank you!
Hi undue_shortage,
This behavior is expected in Power BI Paginated Reports when using cascading parameters. Once you navigate out to a linked report and return, the parameter state is cached, so dependent dropdowns don’t refresh as they would on a fresh load.
A few approaches you can consider:
Independent parameters: Instead of relying on auto‑cascading, bind parameters manually in your query text so they refresh independently.
Navigation links: Use report actions that pass parameters explicitly and reload the report, rather than relying on the browser back button. This forces a fresh parameter evaluation.
Shared datasets: If multiple reports use the same parameter logic, a shared dataset with independent parameters can reduce caching issues.
User guidance: If redesign isn’t possible, advise users to re‑open the report from the app navigation instead of using the back button.
This isn’t a bug but a limitation of how paginated reports handle cascading parameters and navigation. The most reliable workaround is to design navigation links that reload the report with parameters, rather than depending on the back button.
3 Replies
Hi undue_shortage,
This behavior is expected in Power BI Paginated Reports when using cascading parameters. Once you navigate out to a linked report and return, the parameter state is cached, so dependent dropdowns don’t refresh as they would on a fresh load.
A few approaches you can consider:
Independent parameters: Instead of relying on auto‑cascading, bind parameters manually in your query text so they refresh independently.
Navigation links: Use report actions that pass parameters explicitly and reload the report, rather than relying on the browser back button. This forces a fresh parameter evaluation.
Shared datasets: If multiple reports use the same parameter logic, a shared dataset with independent parameters can reduce caching issues.
User guidance: If redesign isn’t possible, advise users to re‑open the report from the app navigation instead of using the back button.
This isn’t a bug but a limitation of how paginated reports handle cascading parameters and navigation. The most reliable workaround is to design navigation links that reload the report with parameters, rather than depending on the back button.
This is very helpful, thank you! I've currently been using the second solution, building a custom back button that passes parameters to the base report, which has been working well. However, is there any option to hide the built-in back button from the linked report?
Can you please give an example of how your experience in this area so we can help you further?
