Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Fabric Ideas just got better! New features, better search, and direct team engagement. Learn more

Power BI - Org apps and cross-report drillthrough

This idea is a request to provide cross-report drill-through capability for org apps. This means being able to navigate between reports hosted in different org apps. The following sections detail why this feature is important for "report navigation." # Some more details We understand a Power BI report as an item that provides users with insights regarding a specific topic. Sometimes, this report contains a semantic model; sometimes, it does not. Sometimes, the group of users is large, and sometimes, it's just me. This is about the relationships between reports and their connectedness. What this idea is not about: This is not about semantic models or the size of the group of users. This is also not about the seemingly everlasting question of whether to create multiple reports with a couple of pages each or one report with all the pages (on a personal note, I consider a one-report solution worse than the dreaded one-table semantic model). From my experience, it seems that when the number of pages gets beyond 12, it makes sense to spread the pages across multiple reports. # Navigating reports, or supporting the decision-making process of report users One of the many reasons reports exist is the simple fact that they are supporting decision-making. Many of my colleagues have feedback that using the cross-report drill-through feature makes it easy to navigate between reports inside the same app. This is important as it prevents "losing thoughts" because a user has to remember how to get to the next level of detail, look at the current context (the current filters) from a different perspective, or ... With org apps new capabilities will become available that will create even more meaningful solutions, but from my perspective it is necessary to enable navigation between reports located in different org apps but inside the same workspace. # Some reasons to spread pages across multiple reports This is a list of reasons why I suggest using multiple reports to my colleagues (not exhausting): + Completely different semantic models, except a few common dimensions like calendar, organization, or ... + I want to share reports with different audiences, but create only one app (currently I'm creating workspace apps). + Multiple report developers build the solution at the same time. + ... # Resources + https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-cross-report-drill-through
Status: New
Comments
UlrikH
Regular Visitor

I share your thoughts on splitting reports. I have several reports in my workspace that have only the calendar as a common dimension. So we created a report and a semantic model for each of these use cases. When everything was ready, we created a report with some kind of key information from all the semantic models and an application for different audiences on top of it. As one semantic model is in another workspace and versioned copies of the reports where not welcome for several reasons, org apps where chosen. So the cross-report drill-through would be very useful to go from the summary to the details in each use case report.