The field 'errors' of the record wasn't found..

[Anonymous]

Hi There.

I have report published to my workspace which has been working perfectly for months.

Out of nowhere I receive this error on scheduled refreshes - > The field 'errors' of the record wasn't found.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

When I'm trying to refresh it manually from Power BI Desktop I do not have this error. It only happens if I want to refresh dataset through Power BI service.

I'm using ODBC Connection and Google Analytics connection and I can confirm that none of them have field 'errors' plus I've never changed anything on report.

[ReportBuilder07]

Hi, I know this reply is very late lol but were you able to find a solution? I used the GA native connector but had some issues with my data too. As a workaround, maybe you can try to test your connection with a 3rd party connector. I've tried windsor.ai, supemetrics and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the GA connector in the data sources list:

After that, just grant access to your GA account using your credentials, then on preview and destination page you will see a preview of your GA fields:

There just select the fields you need. Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url.

[Anonymous]

Yes, I confirm this.

I removed GA just to test it and it works perfectly. I'm commenting this as it might be solution for someone.

[Burningsuit · Accepted solution]

Hi @Anonymous 

This seems to be a general problem with Google Analytics at this time. Many of us have been getting this error on automatic refresh of Google Analytics datasets, it does not appear to happen with a manual refresh.

I must assume Google changed something with their API or Microsoft changed something with their Google Analytics connector. Either way we will have to wait to see if it is resolved.

Hope this helps

Stuart