Forum Discussion

dseelam1's avatar
dseelam1
Regular Visitor
11 months ago

Power BI Desktop fails when applying data source updates

I have updated the data source for some of the tables in the model in Power BI Desktop from SQL-server to BigQuery. I have updated all the column names and functions accordingly and when refreshed da...
Need Help
V-yubandi-msft's avatar
V-yubandi-msft
Community Support
11 months ago

Hi dseelam1 ,

Thanks for posting your query in the Microsoft Fabric Community. The error

ADBC: Could not create dataset _bqadbc_temp_tables

comes up because Power BI’s BigQuery connector tries to create temporary datasets and tables in the background when it runs queries. If your service account only has read only permissions, it won’t be able to create those objects, and that’s why you’re hitting this issue.

To fix it

  1. In the project linked to your BigQuery connection, grant the service account at least the BigQuery Data Editor role. That will let it create the temporary datasets and tables it needs.

  2. Alternatively, you can create your own dataset and grant the service account full access to it, then use that for staging.

  3. After updating the permissions, reconnect from Power BI Desktop and try applying the changes again.

With the right permissions in place, Power BI should be able to create the  _bqadbc_temp_tables dataset automatically and you’ll be able to publish without errors.

Regards,
CST_Team.

dseelam1's avatar
dseelam1
Regular Visitor
11 months ago

After providing data editor privileges to the service account and disabling the Use new Google BigQuery connector implementation option I am getting below error:


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 g4s-data-management/US/job_f778c530_543c_4270_8335_802bd5c0d5ee contained 2 error(s). First error message: Not found: Dataset Org-data-projectUK:UK_Dataset was not found in location US
Details:
DataSourceKind=GoogleBigQuery
DataSourcePath=GoogleBigQuery
AdbcStatus=1
SQLState=
NativeError=0

  • V-yubandi-msft's avatar
    V-yubandi-msft
    Community Support
    11 months ago

    Hi dseelam1 ,
    The service account permissions are fine now, but the error is due to a region mismatch between your BigQuery dataset location and the region Power BI is trying to run jobs in. Aligning the dataset region and the connector region should fix it.

    The error message you’re seeing

    Not found: Dataset Org-data-projectUK:UK_Dataset was not found in location US

    means that Power BI is trying to access the dataset in the US region, but your dataset is located elsewhere (most likely in the UK/EU). BigQuery datasets are region specific, so if there’s a mismatch between the region where the query is run and where your dataset is stored, this error will occur.

    Here are a few things to check

    1. Verify the location of your UK_Dataset in BigQuery.
    2. Ensure that Power BI’s BigQuery connector is set to the same region as your dataset. If the connector is set to US and your dataset is in EU/UK, this error will appear.
    3. Try reconnecting using the new connector implementation and select the correct region for your project/dataset.
    4. If changing the connection region isn’t possible, another option is to recreate the dataset in the region Power BI is using, though this may not always be ideal.

    Regards,
    Yugandhar.

  • V-yubandi-msft's avatar
    V-yubandi-msft
    Community Support
    11 months ago

    Hi dseelam1  ,

    Just following up were you able to fix the issue, or do you still need assistance?

    RayNos ,suggested a workaround that has helped others try removing Implementation="2.0" from your Power Query M code. This may resolve the connector problem and restore access.

     

    Thank You.