Forum Discussion
Power BI BigQuery Connector Fails for Regional Datasets (us-west2) – Works Only with US Multi-Region
- 11 months ago
Hi Siddharthaaman,
Thank you for bringing this up—I see how the dataset region and BigQuery connector can be confusing.
This error happens because BigQuery requires queries to run in the same region as the dataset. If the connector sends a job to US but your dataset is in us-west2, BigQuery will show the message: “Dataset … was not found in location US.”
Currently, this isn’t a BigQuery limitation but a known issue with the new ADBC-based BigQuery connector implementation (Implementation="2.0" in M). There are reports that it can mistakenly default to the US multi-region, which causes issues for regional datasets like us-west2.
1. Does Power BI’s BigQuery connector only support US multi-region datasets?
No, the connector does support regional datasets like us-west2. The error you’re seeing happens because the new ADBC connector sometimes defaults to the US multi-region, even when your dataset is regional.2.Has there been a recent change that removed support for single-region datasets like us-west2?
No change has removed support. What you’re running into is a regression with the new ADBC (Implementation=2.0) connector. Several users have reported this issue starting recently when using regional datasets.3.Is it possible to configure the connector or use the Advanced Editor in Power BI to specify the dataset’s region?
At the moment, there isn’t a region picker available in the UI. However, you can address this by disabling the new connector in Options → Preview features, or by removing Implementation="2.0" from your M query to revert to the stable connector that supports regional datasets. In the Advanced Editor, ensure your source includes a billing project, such as:
Source = GoogleBigQuery.Database([BillingProject="your-project"])
To ensure your SQL queries resolve correctly, always fully qualify table names using the format project.dataset.table.
https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
DirectQuery in Power BI - Power BI | Microsoft LearnThank you.
- 11 months ago
Hi Siddharthaaman,
As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.
Thank you for your cooperation. Have a great day.
Hi Siddharthaaman,
Thank you for bringing this up—I see how the dataset region and BigQuery connector can be confusing.
This error happens because BigQuery requires queries to run in the same region as the dataset. If the connector sends a job to US but your dataset is in us-west2, BigQuery will show the message: “Dataset … was not found in location US.”
Currently, this isn’t a BigQuery limitation but a known issue with the new ADBC-based BigQuery connector implementation (Implementation="2.0" in M). There are reports that it can mistakenly default to the US multi-region, which causes issues for regional datasets like us-west2.
1. Does Power BI’s BigQuery connector only support US multi-region datasets?
No, the connector does support regional datasets like us-west2. The error you’re seeing happens because the new ADBC connector sometimes defaults to the US multi-region, even when your dataset is regional.
2.Has there been a recent change that removed support for single-region datasets like us-west2?
No change has removed support. What you’re running into is a regression with the new ADBC (Implementation=2.0) connector. Several users have reported this issue starting recently when using regional datasets.
3.Is it possible to configure the connector or use the Advanced Editor in Power BI to specify the dataset’s region?
At the moment, there isn’t a region picker available in the UI. However, you can address this by disabling the new connector in Options → Preview features, or by removing Implementation="2.0" from your M query to revert to the stable connector that supports regional datasets. In the Advanced Editor, ensure your source includes a billing project, such as:
Source = GoogleBigQuery.Database([BillingProject="your-project"])
To ensure your SQL queries resolve correctly, always fully qualify table names using the format project.dataset.table.
https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery
DirectQuery in Power BI - Power BI | Microsoft Learn
Thank you.
- v-sgandrathi11 months agoCommunity Support
Hi Siddharthaaman,
As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance.
Thank you for your cooperation. Have a great day.