Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError
- Anonymous5 years ago
Solved!
Changing the Privacy Level in Power BI online as solved the refresh issue.
Having the same issue and not resolved yet.
Thanks.
Hey Rick
Been working through this with MS Support
In short the PBI On Premise Gateway doesnt support any Connection that has a Privacy Level = None.
MS Support showe dme an extract from online learn help pages. So while MS allow you to select None when you create a connection for the Gateway its not supported.
MS simply need to remove NONE from the drop down in the configuration and when that was suggested I was told to add an "Idea". Very frustrating when clearly its not an enhancement or feature we are asking for. Just a way to avoid people like us hours of debugging work.
Here is what I did and haven't had the same error return...
Yes you shouldn't have to do some of the things in these steps but are forced to to get it to work.
1. In PBI Desktop work through each of the Data Source Connections and ensure that you select a Privacy level. Public or Organisational. Use the same across all connections.
2. Publish your report
3. In PBI Service online, add Database connections for your report and ensure they are setup with the SAME privacy level as the report PBIX. All connections must have the same as the PBIX.
4. In you Scheduled Refresh configuration ensure the Data Source Connections from the Report are Mapped to the newly created Gateway Connections.
5. Performs your Gateway refresh.
Something else to mention..
In the PBI Desktop there is a Report option "Ignore Privacy Levels" in the settings for the Report.
This only applies to the PBI Desktop refresh. It is not referred to or used by the Gateway refresh.
So while you think you are telling PBI to ignore Privacy Levels, its the PBI Desktop only that will ignore them.