Forum Discussion
REST api to google big query crashes
we think it was related to having multiple refreshes on the same tables in GBQ at the same time. Since we have organised the refreshes to not run simultaneously it didn't happen anymore
Hey Ju_jacobowiski.
Can you try adding the billing project to the powerquery connection string?
They describe it in the documentation at the very bottom. For me the billing project was the same as the firebase project. (In the form of "monkey-c7c69") After I added that, my refreshes seem to have stopped failing. I don't understand why, but it seems to work. (This might only help if you actually have a project that supports billing)
Quote from the documentation:
You can use Power BI with the Google BigQuery Billing Project. By default, Power BI uses the first project from the list returned for the user. To customize the behavior of the Billing Project when using it with Power BI, take the following steps:
Specifying the following option in the underlying M in the Source step, which can be customized by using Power Query Editor in Power BI Desktop:
Source = GoogleBigQuery.Database([BillingProject="Include-Billing-Project-Id-Here"])
Anonymous
The billing project-id is the Project ID - displayed in the project info card at BigQuery's home page? If yes, I tried it but the error remains. 😞
Hi, all. Thanks Anonymous I managed to sort out this issue. In case someone faces the same problem, here what I've done:
1) Load BigQuery data into PowerBI dataflows, using it as a 'mini' data source.
2) Add the billing-id in the source step (at PowerBi dataflows)
Once it's done, I schedule a refresh between the Dataflows and Google BigQuery, which works just fine. Then I have to change in PowerBI desktop the source of the dataset (from BigQuery to PowerBI Dataflows).
Back to service, I set up the refresh of the dataset to sometime after the refresh of the dataflows is done (I let 2 hours of difference). So far is working fine.
Worth mentioning that Microsoft got in touch with me saying the problem is with BigQuery. But Google BigQuery says the problem is not on their end either - especially because it's possible to update the data through PowerBI Desktop. I hope the solution above help this out.