Forum Discussion
Best Practice - 4 reports, 1 dashboard
Hi,
- We're working on a dashboard which will consist of 4 reports.
- All reports could be using the same dataset, and that is preferred.
- The dashboard will then be shared to several coworkers within the organization with read-permission only.
- We don't have the possibility to create a shared workspace.
Up until now, we've created the dataset together with report A in Desktop, while report B, C, and D were created in Desktop with Live Connection to the same dataset in the Service. This seemed like a good solution since we can re-use the same dataset, and only maintain that one dataset.
However, when the dashboard is being shared to the coworkers, they can't access the reports created with a connection to the dataset in the Service. This was once a bug (half a year ago), but seems to be considered a feature now... https://community.powerbi.com/t5/Service/Share-dashboard-with-content-from-direct-power-bi-connection/td-p/165571
This made us pretty pissed off, because it renders the whole feature of connecting to a dataset in the service useless.
My question is, what is the best way to implement and deploy these 4 reports and 1 dashboard?
Uploading the same dataset for each report seems stupid. We do most likely have to recreate 3 of the 4 reports again, but would like to avoid a similar scenario where some of the reports end up inaccessible.
Thanks in advance!
3 Replies
- AnonymousNot applicable
Are you saying that you don't have the possibility or permission to create a shared workspace to package an app with these 4 reports and 1 dashboard?
Because that would be a good approach to create and distribute the content in your scenario.
If that is your case I can only hope that the app workspace creation process soon will be changed to some better solution (better than the O365-groups solution today)
Br,
Magnus
- HalleriFrequent Visitor
Hi Magnus,
I agree, a workspace would be a good solution for distribution. It's more of a permission-issue, and it's linked to the O365-group creation.
So far the solution seems to be re-creating all reports in the Service. It would work but there's many man-hours ahead, if we can't find another solution.
Regards,
Halleri
- v-huizhn-msftMicrosoft Employee