Shared Datasets?

[kevhav]

Currently I have WorkspaceA, with DatasetX. And I have WorkspaceB, which has another copy of the same DatasetX.

When I change DatasetX (which is large), I have to publish it to both workspaces. And, both workspaces have scheduled refreshes of the dataset. So, in effect, the same dataset is being duplicated in my capacity, and is being refreshed twice. Which slows things down, in my capacity.

Why? Because in WorkspaceA, I have a set of "production reports" that I want to keep secure – I don't want other users to be able to edit them. But my users do need to create/edit their own reports; that's why I created WorkspaceB – there, they can do so.

And, as far as I know, (a) I cannot put all the reports in the same workspace, because if a workspace member has permission to edit reports, then they could edit all reports, including my "production reports;" plus (b) two workspaces cannot share the same dataset.

But I was just at the Business Applications Summit, and somebody there said that it should not be necessary to have two copies of my dataset in two different workspaces, because instead I could set up "shared datasets." Is that true? Is that a thing? Is that something that is coming?

Or...is there (or will there be) any "better" way to meet my requirements, without needing to store and refresh two copies of my dataset, in my capacity?

[Anonymous]

I think the comment was made without understanding your particular concerns and PERHAPS with a nod to what is coming.

1.  If you had a shared dataset, then you would only need it in one workspace but as you mention, the permission structure wouldnt match your needs.

2.  One of the changes announced at the Biz Apps Summit was that the permission model was changing so that you would be able to create 'read-only' members in a workspace along with 'edit' members.  At that point, you could then revert to a single shared dataset.

I haven't gotten any indication of when its coming but very much hoping that its soon because we need this capability now as well.

[kevhav]

Thanks for your comment, @Anonymous ... 

About 'read-only' members in a workspace along with 'edit' members -- even if/when that comes, I don't see how it would help with my problem. I still wouldn't be able to have a single dataset; and allow a given user to create/modify their own reports from that dataset; and also prevent that same user from modifying/deleting the "production reports," which are also built on that dataset.

[v-piga-msft]

Hi @kevhav,

For your scenario, you may could try with content pack which your user could make a copy and edit their reports with the same dataset but not affect your report.

You also could post your idea in Power BI ideas forum and add comments there to improve Power BI and make this feature coming sooner.

Best Regards,

Cherry

[Anonymous]

I think you are right, unfortunately, I didn't think that one through.  What you need is fine grained permission on the individual reports or sets of reports.

[Anonymous]

I took a shot and asked on Twitter if this would be included in the new workspace experience but I got a 'no comment at this time, watch the blog'.  Patience was never my strongest point 🙂