Forum Discussion
Sharing Reports
- 10 years ago
Anonymous Erm - I would have proposed to publish the report to his own PBI account, create a PBI group, then either a) create content pack and import report into group or b) upload PowerBI file into group.
Did you exclude that on purpose or did I miss sth here? :o
// Was he referring to the desktop app only?
Assuming you understand this: A Dashboard tile when clicked will send the user to your report, where they can see all the pages.
Here are all your options:
1) Send them the PBIX file
2) Read Only Option - push the report to the Service, Pin a visual to a dashboard, and share the dashboard with your colleague.
3) Read/make personal copy - Push the report to the Service, Create a Content Pack with only your report, give your colleague access to the Content Pack, and have him connect to the content pack.
There is no direct capability to share a report in the same "Read Only" way as when viewed via the shared dashboard mechanism.
Anonymous Erm - I would have proposed to publish the report to his own PBI account, create a PBI group, then either a) create content pack and import report into group or b) upload PowerBI file into group.
Did you exclude that on purpose or did I miss sth here? :o
// Was he referring to the desktop app only?
- Anonymous10 years agoNot applicable
Bjoern Thanks for the feedback.
I took the question as it relates to sharing a single report. I look at Groups as collaborative spaces, not spaces to import users and pull things in to the group in whatever manner to "share".
I agree that a workable option would be to pull the file into a Group, and grant the user "view" perms, but I didn't assume that there would be a whole set of reports they should have view ability for.
I did recommend Content Packs as an option, personally I wouldn't recommend using Content Packs in the way you describe primarily due to my view of how to utilize Groups. (Although it may work)
- WillT10 years agoCommunity AdminYou're both right - Groups would be an option to share the report specifically, but it's a workaround and not intuitive :) This is something we want to fix in the future! Thanks