Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
I have a dashboard which provides itinerary summaries by continent. This is also a common scenario where you have a top-level buiness summary and several breakouts to provide context. In my example, each map is simply a filtered view to the same report. We want comparative context all in one place, hence multiple maps. When clicking through, there is no effect on the report filters, they are set to whatever was last applied. I've looked for ways to parameterize the linkage, and am pretty sure there is no such capability. We do NOT want to apply custom URL's, need to keep the user in the same app context. The pragmatic solution for now is providing a few button bookmarks and letting the user apply the filter when in the report. This is effective but difficult to explain why the app does not maintain context. Looking for ideas.
Solved! Go to Solution.
Amazing, I actually learned something, namely a big DUUUHHHH**. I compared what happens when I click the "internal" link with the custom "external" link options for my report. They are the same. I'm guessing I never noticed because the GUIDs in the links were not easily memorable. The proposed solution works. And my concerns about losing context are irrelevant since the dashboard does not appear to be "connected" to the reports in any way, as can be observed using a bookmark "back" button, they only work within the report itself, never back to the parent dashboard.
** because was an ASP.NET developer in the prior decade, everything was glued together only with URL + query parameters.
A follow-up note on the linking issue. It looks like the common solution for a reporting hierarchy like this (top level + divisional breakouts) is to duplicate the base report tab and then apply page-level filters. The source dashboard would then have items pinned from their respective "clones" and standard linking would apply. Thinking as a developer, it makes more sense to have one report and apply filters selectively. However, most business analysts think in terms of Excel, where you would, indeed have multiple layers, each with their own worksheet tab. The consolidated tabs would then use native Excel functions for the rollups or aggregations.
Sometimes you need to step back from "elegant" to "kludge" when the client prefers to retain old habits. No problem, either solution works. The amount of dashboard pinning is the same for either.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
45 | |
34 | |
32 | |
25 | |
23 |
User | Count |
---|---|
34 | |
33 | |
21 | |
20 | |
15 |