Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi All,
I am currently navigating from one Power BI report to another within a Power BI App using a button with a Web URL action. The navigation itself works correctly—the target report opens as expected—but I am facing issues with filter context not syncing properly.
Is this behavior expected when using URL‑based filters between reports in a Power BI App?
Are there any recommended best practices to ensure that:
Any guidance, known limitations, or alternative approaches (such as cross‑report drillthrough or model alignment considerations) would be greatly appreciated.
Thank you for your time and support.
Solved! Go to Solution.
Hello Use cross-report drillthrough on a shared dataset it preserves filter context natively. If you must use URL filters, ensure theflter= parameter matches the exact model table/column name (DimStudy/study_id, not the display name), and point to the workspace report URL rather than the App URL.
Hi @Mukta,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @pankajnamekar25 and @cengizhanarslan for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi @Mukta,
We wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Cross-report drillthrough is the recommended approach for passing filter context between reports in the same App:
Hello Use cross-report drillthrough on a shared dataset it preserves filter context natively. If you must use URL filters, ensure theflter= parameter matches the exact model table/column name (DimStudy/study_id, not the display name), and point to the workspace report URL rather than the App URL.
Thankyou Pankaj, I will try this out
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.