Big Query refresh error in Power BI Service

[Anonymous]

Hello experts,

I'm connected to a view in BQ which refreshes normally through PBI desktop, but when publishing dataset to PBI service it gives this error:

• Data source error {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: VU_Budget_Tracker_AGG.
• Cluster URI WABI-CANADA-CENTRAL-redirect.analysis.windows.net
• Activity ID 4fbdeb64-8d55-4667-9f2a-683f3c353b82
• Request ID 648dfc6f-bcfb-1b9f-9a03-9c7df996e0a6

Any idea why this is happening?

Thanks,

[Anonymous]

Hi @Anonymous,

Did you update your data structure on your data source side? Have you mixed both on-premise and online data sources in your report? Since we not so clear about your scenario, can you please share more detailed information?

Regards,

Xiaoxin Sheng

[Anonymous]

Hi Xiaoxin,

No changes to data structure, and yes mixing on-premise and online data sources.

These are the query steps for the table in the error:

Source (Big Query Import) > Navigation > Renamed Columns > Appended Query (another query with same column names from excel).

Please let me know if you need more info.

Thank you,

M

[Anonymous]

Hi @Anonymous,

Please create a duplicate query form the current query table and extract the parameter tables that used in the append query step to check if their data structure changes.

In addition, did this 'rename step' new added to your query table steps?  If this is a case, you need to check below the original table query steps which used old field names and manually fix them with new column names.
Notice:  Power query will cache the table structure into query steps, these structures do not auto-update.
Regards,

Xiaoxin Sheng

[Anonymous · Accepted solution]

Hi Xiaoxin,

I was able to fix it by removing the appended query step in Power BI and appending the data in Big Query before pulling it into Power BI.

Thank you,

M

[Greg_Deckler]

Well, it doesn't like something in your VU_Budget_Tracker_AGG table. Other than that, it is a mystery.

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".