Directquery for datasets only needs read permissions on all datasets

[bi65]

The new preview feature DirectQuery for Power BI datasets is very useful https://powerbi.microsoft.com/en-us/blog/directquery-for-power-bi-datasets-and-azure-analysis-services-preview/ However, its a limitation that the user has to have build permissions on the dataset linked to by direct query. I want to use this feature, but don't want to give the report users build permissions. I would expect that read permissions would be sufficient.

[GD09012]

Seems to me this is a major limitation of the new feature, surprised that this idea is not geting more votes/attention.

[hornsjd1]

I agree, this feature is non-functional for any enterprise deployment and also does not allow a PBI Premium subscription to be leveraged because all users need a pro license. Which to me is a bit ironic, because it would most benefit the enterprise environment (those environments could most leverage dataset re-use). I was very excited for this feature, but cannot use it until this is corrected.

[eadere]

This seems like a simple issue to fix, if the Direct Query is published after merging two datasets or sources, it should be available to all users. Imagine if Excel charts could only be seen by certain front end users, it defeats the purpose. Our company has many projects waiting for this to be resolved.

[olga_iatsenko]

Really needed! Please implement!

[sasha_calderwoo]

essentially for it to be used with an enterprise model

[jashwood]

If not for the presence of other similar bugs, this would be comical.

[s_strandstra]

This is indeed very necessary in order to achieve self-service BI on an enterprise level

[Sridhar_Ammula]

Golden Dataset is a great methodology but unfortunately we cannot use it as we have to give build permission to end users. It will be great if we can limit this to Viewer role only without requiring to have Build permission.
 

[nishalit]

we are currently looking at this but don't have an exact date yet.

[franck4]

This feature is great but not usable in business case because of this limitation 😞