Forum Discussion
BigQuery Dataset not found in Power BI Service – Gateway MashupDataAccessError
Hello my friend, thank you for your help. Let me explain what happened.
In my queries that were pulling data from BigQuery, I was using a table called DataLakeforUsers. Until yesterday, everything was working normally and refreshing without any issues.
Then I got that classic error related to Implementation 2.0 when trying to pull the data. I removed the Implementation="2.0" parameter, but after that, another error appeared and I got stuck.
In summary, the issue was that I needed to explicitly specify which dataset/project the table belonged to. That was why BigQuery couldn’t find it in the US region. So I updated my queries to use FROM projectname.DataLakeforUsers, and after that it correctly identified where the data was coming from and everything started working again.
What I found strange is that this error happened suddenly, without any clear explanation, since it had been working fine before.
Anyway, thank you again for your help I really appreciate it.
Hi YC1218
All reports are always rendered via the Power BI service. So if you set up a schedule refresh in the Power BI service, your users will then see the updates to the data. If you make changes to the visuals in the Power BI report, you will then have to upload that into the Power BI service for your users to see the change.
Hello my friend, thank you for your help. Let me explain what happened.
In my queries that were pulling data from BigQuery, I was using a table called DataLakeforUsers. Until yesterday, everything was working normally and refreshing without any issues.
Then I got that classic error related to Implementation 2.0 when trying to pull the data. I removed the Implementation="2.0" parameter, but after that, another error appeared and I got stuck.
In summary, the issue was that I needed to explicitly specify which dataset/project the table belonged to. That was why BigQuery couldn’t find it in the US region. So I updated my queries to use FROM projectname.DataLakeforUsers, and after that it correctly identified where the data was coming from and everything started working again.
What I found strange is that this error happened suddenly, without any clear explanation, since it had been working fine before.
Anyway, thank you again for your help I really appreciate it.