RussellPrice's avatar
RussellPrice
New Member
3 years ago
Status:
New

Report Shortcuts Across Workspaces

The concept of OneLake and data shortcuts to reduce the duplication and maintenance of data tables is Awesome!


Similarly, an organization may want to manage report access by domains and workspaces, but there is a report that is necessary to be shared to multiple domains/groups. The desire is to maintain the report in both workspaces so that each group can have access to it. however, this requires 2 copies of the report to be maintained any time there are changes (difficult to maintain), OR a new workspace created that both groups can access (in some cases is not practical). The ability to create a Shortcut in workspace 2 to a report in workspace 1 would be helpful as the shortcut would grant access to the report for users of workspace 2 for that specific report without sharing the entire workspace or duplicating the report, increasing the maintenance/governance/deployment time and cost. With the Shortcut capability both groups can be looking at the Same Report without question of if the report in workspace 2 is the same version as in workspace 1.


Considerations: The Shortcut report would not have the edit option for anyone, only the source report can be edited.

5 Comments

  • We have the same problem and it's very dificult to mantain.

    It would be better to manage through shortcuts.



  • This is especially useful when you have a dev, a test and a prod workspace for data engineers, but you don't want to have equivalents for all business domains. Having lifecycle management on report user/business domain workspaces would lead to 50+ workspaces for my customer, making it difficult to oversee. However, the business domain workspaces are useful for granting access on groups of reports.


    The current alternative is using the data engineering prod workspace for all reports. The reports are grouped in folders to make it easier to oversee, but we grant access to Entra ID groups report by report.


    In the Fabric deployment pipeline, we would still see all those reports and other artifacts ungrouped, which looks quite messy as well.

  • This is especially useful when we have org-apps instead of many powerbi/workspace-apps. Our customers can get access to one org-app instead get access to many pbi-apps.
  • This is especially useful when we have org-apps instead of many powerbi/workspace-apps. Our customers can get access to one org-app instead get access to many pbi-apps.

Recent ideas