Read-only dataset publlished on service

[bpasol]

Hi,

I created a dataset in Power BI Desktop and published it to a private workspace where I am admin. I would like to allow members to create and share reports (in the same workspace) based on that dataset, but prevent them from downloading, overwritting or deleting the dataset pbix.

Is there a way to achieve this at the moment? 

Thanks!

B.

[v-juanli-msft]

Hi @bpasol

You can create an organizational content pack with this dataset and publish and give access to the members.

They can get the organizational content pack with this dataset, they can't make a change of the dataset until they make a copy of it. Then they can create a report based on the dataset.

Intro to organizational content packs in Power BI

Create and publish a Power BI organizational content pack 

Organizational content packs: Copy, refresh, and get access

Best Regards

Maggie

[bpasol]

Hi Maggie,

I published the dataset to a content pack and shared it with a coleague. He is able to import the content pack and he sees the dataset in his workspace, however he cannot create any new reports from it:

 - no new report button (as visible in screenshot below) in the dataset section

 - create report in app.powerbi.com and Get Data in Power BI Desktop don't show the dataset in his My Workspace. 

Any idea why, did the deprecation kick in already or is it possible I did something wrong when sharing the content? 

Thank you!

[v-juanli-msft · Accepted solution]

Hi @bpasol

Click on the three dots and select "make a copy", then from the copied dataset, he can create a report.

 

Best Regards

Maggie

[Anonymous]

Hi I am not sure if it's a solution. Users still have the possibility to download the pbix , amend the model and publish to the same workspace and overwritting the orifinal model I can see a gap in terms of dataset governance. Thougts?

Maybe the 'viewer'role will help? when is it planned for release? 

Cheers,

Ludo

[bpasol]

Thanks Maggie!

[bpasol]

Thank you, Maggie! I will be looking into that.

The only concern I have is that MS is deprecating this feature, so I'm a bit worried I will have to re-do this part of the solution in a year's time when Apps is more mature.