create multiple apps from same workspace
create multiple apps from same workspace infect from same Dataset without replicating the dataset multiple times.
only option we have now is to update the app and only one app per workspace can be created which a kind of restrict the workspace usability.
If we can create multiple apps share it with different users without creating multiple workspace ... means same dataset no dataset replication, will save the storage as well.
Currently we are not planning to allow multiple apps to be published from one workspace. Soon we will allow you to discover and use a dataset across workspaces. Once we have this capability, we believe much of the need for multiple apps per workspace will be addressed.
The problem isn't dataset sharing. The problem is scalability and security. We'd have to have many versions of Apps in order to make sure groups are only seeing the reports they need access to. 1-1 App to workspace forces duplicate reports to be hosted in numerous workspaces to customize the app experience each group is getting. This means more reports upkeep not just datasets and also more workspaces to maintain which means access slippage.
Dan Green commented
This is absolutely needed to rival other platforms like Qlik. We were planning to use workspaces as a UAT type situation and publish to apps once finalized. This does not look like we can do this now. In Qlik, you can have multiple apps per stream.
Anbarasan Dhanushkodi commented
This proves Power BI is not ready yet for Enterprise Level BI Implementation. Quite surprised to see how this idea is turned down just like that.
We have reports built for about 10 different departments with specific Dev, UAT and Live environments. Because of Workspace 1-1 relationship we are stuck with 30 workspaces. I hear Lukasz point that shared dataset address the part of the problem by not building many datasets for the same visual representation of the model i.e. in Dev, UAT.
The request here is, how you bundle and deploy contents of workspace to different security groups isolating each other such as sales, marketing and customer care.
@Lukasz can you explain why you believe shared dataset will address the need of multiple apps per workspace?
This feature is still very much required. I want to upload and refresh one version of a report and allow it to be to visible to different groups of staff via apps. I do not want to have to schedule the same report to refresh multiple times which having it in multiple workspaces would force me to do. Please add this feature.
Limiting to one app really limits central reporting as getting up to director level summaries are such a hassle of wading through the detail needed for other reporting bodies. All of these report levels come from the same data source so it would be a painful act of duplication to produce multiple workspaces for these, especially with the limited ability to pull information between workspaces. Please reconsider!!!
The proposed direction will result in the continued growth of Workspaces in our organisation. This is a real hassle when my group manages a central reporting function. If the Workspace numbers continue to grow then we will need a good way or organising them rather than just a flat list of Workspaces on the Power BI service
Remi Arial commented
It's a disappointing response.
We are now rethinking the way we work with workspaces and having more than one app would be perfect for our need.
Jose Maria Betegon commented
Really needed if we want to use apps to share reports to users
Wally Tinsley commented
very disappointing response. Vithal's comment from 9/4/19 is a perfect description of the way this needs to work. A single app is basically useless. The need is to be able to select from the reports in the workspace and publish an app for a single individual or a select group within the larger organization or a group outside the organization. What organization wants to share all reports with all parties? I struggle to understand the position stated in the admin response.
It will be wonderful to have this, as our B2B business and B2C business can have better synergy from the insights of products and solutions from same dataset, while getting ease of use for multiple perspectives.
Stuart Swartz commented
This is disappointing to hear... clearly based on the comments the community does not believe this functionality will be properly addressed by shared datasets. I certainly don't. I hope you reconsider and add this functionality.
Why do I want to share a dataset when all I want to do is share a subset of reports in a workspace? This does not make any sense. If I have 50 reports in a workspace and out of which I want to share 10 reports with Sales, 10 with Marketing, 10 with Finance, 10 with Tax and remaining with IT, It would have been great if we could create five apps and add reports to the apps accordingly. But as of now, the only way is create five different worksapces and one app per workspace. I cannot see how allowing discovery of datasets across different workspaces addresses this requirements.
Power BI uptake will increase by many folds if this feature is implemented. This is not only a great way of keeping content in one workspace and sharing with different teams, this will also take care of security.
Please reconsider your decision not to allow multiple apps for worksapce. A big opportunity wasted.
+1 to everyone on this thread who has described the need to publish different apps for different user groups who need different subsets of the same reports. The new app navigation is lovely, but quickly becomes overwhelming with a lot of reports in one app. Not all of our users need all of the reports, so we'd like the option to streamline their experience without creating a maintenance nightmare for our report development team. Publishing multiple apps from same workspace would help. Unless there's some other approach to personalization for report consumers on the way...? Something tied into security permissions would also potentially help us (ex: hide report from the app nav if user isn't in a security group with access to that report)
Camille Guedj commented
Shared datasets do not solve the issue underlying this idea at all.
Let's say you developed 3 reports (R1, R2, R3) and you have 2 types of audiences (A1 and A2). Both audiences can access R1. But for data privacy issues, only A1 should access all three reports.
Without the possibility of creating 2 seperate apps from the same "developer" workspace, you need to create two separate "publication" workspaces: P1, where only A1 has access and all three reports are published, and P2 where A2 has access and they can only see R1.
It's fine as long as only the data refreshes are needed. But as soon as you make a change to R1, you need to re-publish it once for every publication environment you have!
Now imagine that across dozens of projects, for dozens of audiences, and you got a very time-consuming, error-prone process...
I concur with the others re: this topic. Adding the ability to publish multiple apps from the same workspace simplifies the environment by reducing workspace clutter and helping to enforce separation of published report, dashboard, and dataset staging from the target applications. The architecture already supports access control separation, this is just the next logical step that is really necessary for enterprise deployment cases
Lukasz, the proposed solution of allowing datasets to be used across workspaces in fine, but it doesn't at all solve the problem in the original idea. Multiple apps from a single workspace will solve a great number of user issues outlined in the comments.
Samuel Natamihardja commented
I found this ideas because of Curbal youtube channel, and one of the commentor is mentioning about this.. I think this ideas is very excellent if you're thinking on business users perspective.
Previously I wasn't aware of this issue since I'm the developer. But when it is brought up, I realized that not all of users familiar with this tools.. so that being said, UX is the key for business users..
go for it..
i think it is a basic feature to help reduce the number of workspaces. I work in a big company and we have many duplicate workspaces for this reason. for example for group a we want to see report a and b. for group b we want to see report a and c. Current solution is two workspaces and report a refreshes everyday two times. Imagine this situation in a big company.
Kirill Perian commented
In consulting, we always start out by creating one collaborative workspace with prototype datasets for proof of concept purposes within clients' PBI Tenant. Oftentimes, they have restriction on how many workspaces can be created within their PBI Tenant. However, if multiple apps can be allowed per workspace, this solves a problem of spinning up numerous workspaces per each combination of users that need access to specific content. Please reconsider this - it is a very, very common use case.
You should really get the team to reconsider this. I cant see how this would be an efficient use of resources. You would get a lot of additional workspaces created for no real benefit.