Forum Discussion
Share your thoughts on DirectQuery for Power BI datasets and Azure Analysis Services (preview)
I'm having the exactly same issue on my end. I believe it is related to problems with build permission. The publish work correctly when you connnect to datasets located in a workspace you are member of. The above exception occurs when you try to publish a report which utilizes Direct Query connection to a dataset you only have build permission to but are not a member of a workspace it resides in.
I have a support ticket opened on this but it is progressing painfully slow.
you need build permissions on the full chain at the moment.
- jpierzchala5 years agoAdvocate I
I'm not entirely sure what do you mean by that.
My experience is that if you have a build permission to a dataset you can build reports on top of this dataset (using live connection mode) and publish to service even if you're not a member of the workspace, the dataset resides in.
However, the moment you change to DirectQuery mode (the "make changes to this model" option) publishing no longer works due to the exception above - Anonymous5 years agoNot applicable
I added dataset as datasource to an existing file with other datasources as well. now I see the dataset in the Fields pane on the right and in the Model view, but when I hit Transform data the dataset does not appear in the Power Query editor...
For exampke I wanr to merge existing data source with data from dataset - how can it be done?
thanks