BigQuery Connector gives erro: reporting was not found in location US when exported to Service

[GB_22]

We are using the BigQuery connector to show data from Google Analytics over PowerBI.

In BigQuery our datasets are single region in EU, europe-west8.

In PowerBI desktop the connectors work fine, when we share the model and the dashboard we recieve this error:

Underlying Error: PowerBI service client received error HTTP response. HttpStatus: 400. PowerBIErrorCode: QueryUserError
QueryUserError: DataSource.Error: ADBC: Cannot execute <ExecuteQueryInternalAsync>b__1 after 5 tries. Last exception: The service bigquery has thrown an exception.
No HttpStatusCode was specified. Job xxx-xxx-xxx2/US/job_ad581dd2_32c9_48bc_9f03_67054ebed782 contained 2 error(s).
First error message: Not found: Dataset xxx-xxx-xxx:reporting was not found in location US.
Microsoft.Data.Mashup.ErrorCode = 10941. DataSourceKind = GoogleBigQuery.
DataSourcePath = GoogleBigQuery. AdbcStatus = 1. NativeError = 0. . The exception was raised by the IDbCommand interface.
Correlation ID: 29dc5d58-c338-dd28-cc07-e6f0b760f0c0
Activity ID: ace4521f-3f9d-47ad-a272-ca20089ffec0
Request ID: f27c4318-807e-f26a-03e6-403c610df8fc
Time: Mon Sep 22 2025 13:46:21 GMT+0200 (Ora legale dell’Europa centrale)
Service version: 13.0.26686.38
Client version: 2509.2.25971-train
Cluster URI: https://wabi-west-europe-redirect.analysis.windows.net/

We've used this in the past since before august circa, suddenly it stopped working.
Do you have any advice?

Regards

[BeaBF]

@GB_22 Hi! Here a few tentatives:

1. In Power BI Desktop, go to Options → Preview features and disable “Use new BigQuery connector implementation” (or similar). Then re-publish the report. Many users report this restores correct behavior for regional datasets.

2. In your queries’ Advanced Editor, locate the BigQuery source lines (something like GoogleBigQuery.Database(...) with optional arguments) and remove or override the Implementation="2.0" parameter. Some users say removing it fixes the location mis-targeting.

3. Make sure your M code or connector config explicitly includes [BillingProject = "your-GCP-project"] and references tables as project.dataset.table. This gives the connector more context about which project to use. Some forum users reported this helps.

Let me know if one of this works.

BBF

💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!