Workspaces and apps should not be as closely coupled as they are today. Workspaces are often used as collaboration and sharing areas within a team or division in the company, while apps are containers where you gather content for a specific target group of consumers. Even if we change our mindset and treat workspaces as containers for a specific target group instead, we still have issues since there are a lot of content that should be consumed by several different target groups, but not all content targeted for one group should be consumed by all members of of another group. By todays design this means that we have to duplicate the same report in different workspaces to pack it into different apps. If apps and workspaces could be decoupled we could create an app for a specific target group and cherry pick reports and dashboards from different workspaces to be featured in that app. That would be good.
2 Comments
- pivers11New Member
I think this a great idea. Whereas you can embed links to other workspaces you get the login prompt each time. Since App security is not related to workspace security, it seems like it's not required to be a workspace feature. This would allow many to many app to workspaces.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Support external tables for parquet/csv in Fabric DW
Fabric Data Warehouse allows reading Parquet and CSV files using the OPENROWSET function. However, it does not support external tables that reference Parquet or CSV files (CREATE EXTERNAL TABLE (Tran...jovanpop-msft2 hours agoMicrosoft EmployeePlanned2.9KViews38likes3CommentsFabric warehouse SQL editor: improve Ctrl-Enter
Today the Fabric warehouse SQL editor executes the full text in the editor when you press Ctrl-Enter without anything selected. It would be very convenient if Ctrl-enter only executed the single sql...stegus643 hours agoNew MemberNew17Views0likes1Comment