Power BI refresh not working. OData connector

(0) Share

Report

Posted on by Richard Mayo

Is anyone else having this issue... seems to have started with the 17.4 update.

even starting a brand new PowerBI file it still it giving this error also happening on multiple tables

86CB5D4F_2D00_B270_2D00_42B0_2D00_A20B_2D00_97FB4AF4D48A.png

I have the same question (0)

All responses (8)

Answers (1)

Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

If this issue is happening after an update from Microsoft in the SaaS release, feel free to raise it to Microsoft as an issue via your CSP / Dynamics Partner.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Steven Renders 5,672 Moderator on at

Like (0)

Report

Strange, here's it's working fine.

Is there more information in the details?

Also, why are you using ODATA and not the Power BI Business Central connector?

Was this reply helpful? Yes No
Richard Mayo on at

Like (0)

Report

That’s the strangest thing, we are using the Business Central connector.... never used OData before

Was this reply helpful? Yes No
Steven Renders 5,672 Moderator on at

Like (0)

Report

Ok, I understand. Don't worry, the BC connector uses ODATA behind the scene ;-)

Do you have any special characters in your company name? Like a / or a \ or an ' ?

Was this reply helpful? Yes No
Richard Mayo on at

Like (0)

Report

No special characters.

We did recently change to M365 Business Premium to get better security features. Would that have something to do with it? Perhaps my account (which is used for the credentials for the Business Central connector) has some security that’s preventing the connection working properly?!

Was this reply helpful? Yes No
Steven Renders 5,672 Moderator on at

Like (0)

Report

In Power BI Desktop, options, data source settings, try to clear your credentials and then try to import data again. Does that work?

And the user you select, which permissions does he/she has in BC?

Was this reply helpful? Yes No
RustyAustralis 202 on at

Like (0)

Report

I suddenly got the same issue. On 17.4 SaaS with only Essentials license. Interestingly I have data sets using o data directly and those using connector. Only connector fails. The sooner MS allows anyone to submit a request with different SLA response times and have the nominated partner collaborate the better. It will make the service much less fragile. Ongoing issue at the moment. I think it’s something to do with how the connector itself is working.

Was this reply helpful? Yes No
Verified answer

Richard Mayo on at

Like (1)

Report

Our MS Partner has escalated this with Microsoft and they have confirmed they are aware of the issue. There is a hotfix in production and the estimated ETA is around 4 days.

Hopefully that will fix it.

Was this reply helpful? Yes No