Forum Discussion
PowerBI Service Scheduled refresh error for Google Analytics
Hi Everyone,
I am connecting to Google Analytics from PowerBI using GA connector v2. The connection works fine when I use the PowerBI Desktop to create the report.
But, one I upload the report to the PowerBI Service and try to create a Scheduled refresh, I get the error "Failed to update data source credentials: We found an unexpected character in the JSON input." while editing the credentials. I am using OAuth2.0 Authentication with organization Account Type. This same type works fine in PowerBI Desktop without any issues.
We have been using same type of workflow for other reports in the past and they are/were working fine. Have anyone encountered this issue? Is there any workaround to this except for using BigQuery??
Please help.
Thank you!
Hi all, this has been resolved by devs it seems. I went to check if I could put my report back on scheduled refresh just there and it is now working again. So, the token issue that I am assuming was preventing the connection from Google Analytics to Power BI is now working fine.
12 Replies
I have as recommended by Anonymous raised a support ticket, I got called by support and they told me the devs are currently aware of the problem and are moving towards a fix shipped by the end of this month May 2025, but no promises, only estimations. If the bug still persists after the end of May, then we should inquire for more information/status.
Hi all, this has been resolved by devs it seems. I went to check if I could put my report back on scheduled refresh just there and it is now working again. So, the token issue that I am assuming was preventing the connection from Google Analytics to Power BI is now working fine.
Hi COS019970,
I'm glad that your issue has been resolved. As you have already stated the reason for the issue to occur and confirms that your issue has been resolved, can you please mark your reply as solution so that other community members can find it easier to solve relevant issue.
Best Regards,
Hammad.
I can confirm that this issue has been resolved. I have been with MS support throughout and they have deployed the fix for this issue.
Hi pawankarki23,
Thanks for reaching out to the Microsoft fabric community forum.
This is a known issue currently affecting the Google Analytics (GA) connector v2 when used in the Power BI Service. While the connection and data refresh work correctly in Power BI Desktop, users are experiencing the following error when attempting to configure scheduled refresh in the Service "Failed to update data source credentials: We found an unexpected character in the JSON input."
This typically occurs during the credential editing process using OAuth 2.0 with organizational account in the Service. Based on current understanding, the issue appears to be related to how the Service backend handles the OAuth response returned by Google, potentially due to a change in the response format or a parsing issue in the connector implementation.
As this issue is limited to Power BI Service. Desktop continues to work as expected and other Google-based connectors like BigQuery may not face this issue due to a different authentication flow.
At this time, there is no confirmed workaround using the GA connector v2 directly in Power BI Service. We recommend opening a Microsoft support ticket if you're a Pro or Premium user so our team can escalate and gather more diagnostics.
Reach out to Microsoft Support by raising a ticket with Microsoft Support. Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnIf I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi pawankarki23,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Hi, I also have this problem and can't find a solution that works.
