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.

p_subasinghe's avatar
p_subasinghe
Regular Visitor
11 months ago

I am having the same issue.  However, I get the error when I am adding a data source.  I can select BigQuery, and navigate to my project, but when I try to open a folder in the schema, I get the same error.

 

The service account I am using has admin credentials, so it does not seem to be a permissions issue.

 

This is also a brand new issue.  I have been using the same service account and credentials succesfully for over a year.  Suddenly, I get this error.

 

I am thinking this is a microsoft issue that needs to be fixed.  I am able to query the data source directly with M code as a workaround.  But it is a pain to not be able to select tables from our DWH from the GUI.

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

    Hi p_subasinghe ,

    Here are some steps that have helped others in similar situations.
    If you’re using the legacy connector, try removing Implementation="2.0" from your M code. This will trigger fallback behavior, but note that it may default to US settings unless you specify otherwise.

    Reconnect using the new connector and check that the region matches your dataset. If you continue to see errors in the GUI, consider submitting a ticket to Microsoft, as this could be related to a recent connector update or a change in default behavior.

     

    You can raise a support ticket with the Microsoft team they’ll review the issue and get in touch to help resolve it.
    How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

     

    Thank You

     

     

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

      Hello p_subasinghe ,
      If you have received any updates or replies from Microsoft Support, please share them here. Your experience could assist other community members who are dealing with similar issues.