Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
As far as I have been testing around I've tried to get to a point where I can align some best practices for our organisation regarding PowerBI. Now what we're trying to accomplish is that we're able to create and/or maintain reports with multiple developers.
So I was thinking about the following solution;
1. We're creating one or more central PBIX files with the desktop app in which we maintain the datasets ass datasets cannot be created within the service.
2. We set a scheduler on the data to keep it fresh.
3. All reports (eithe created within the service or within the desktop app) will be using the PowerBI data source described above.
4. As you can only create 1 (multiple paged) report within every PBIX it makes no sense keeping the PBIX files locally. You need them on a central place for another developer. However, PowerBI gives the option to download them back from the service, so why storing them somewhere else anyway?
5. In the end we use the service to create dashboards and distribute them via an App.
Is this the best way forward or are there any suggestions?
Hi @dirkmuis ,
For the forth point mentioned above, you could create an App Workspace, add those developers as members with edit permission so that they can make changes to reports within workspace and make others to be able to access updated report.
Regards,
Yuliana Gu
Hi @v-yulgu-msft ,
At the moment we're sharing a central PowerBi account so changing things in the service will be no problem. The challange is changing things in the Desktop version. I think we need to keep the pbix files on a (onedrive) storage and don't work on them at the same time.
For publishing I created 3 workspaces
-DEV => development
-TEST => customer testing (app or dashboard sharing)
-LIVE => live (app)