Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello,
Yesterday we had a a few scheduled refresh failures, but today almost all of our datasources are are failing to refresh. All of these have to do with Business Central Web Services datasources. Here is an example of the error given: Expression.Error: The OData connector failed with the following error: We cannot convert the value null to type Record... . The exception was raised by the IDbCommand interface. Table: Division.
Using the desktop app I can refresh the datasources perfectly fine, but the PBI Service fails. I have gone through and reselected the datasource in the naviagtion step and then republished the to the workspace to test. After this the datasource refreshed without error, but upon the next scheduled refresh the datasource failed again with the same error. This leads me to believe that there is an issue with the PBI Service or Business Central, but as the Desktop app refreshes correctly it seems more likely that it is the PBI Service. Anyone else having similar issues?
Solved! Go to Solution.
@desac @MattRTemcool @MaryAnne @omgull @OttoChr
this solution worked and I've tried it
Have you tried the fix on the below link?
https://www.reddit.com/r/PowerBI/comments/1f7yadg/data_conversion_error_on_refresh/
We encountered the same error and by adjusting the 4th parameter on the API call, the problem went away
Before:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, null)
After:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null])
Proud to be a Super User! | |
@desac @MattRTemcool @MaryAnne @omgull @OttoChr
this solution worked and I've tried it
Have you tried the fix on the below link?
https://www.reddit.com/r/PowerBI/comments/1f7yadg/data_conversion_error_on_refresh/
We encountered the same error and by adjusting the 4th parameter on the API call, the problem went away
Before:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, null)
After:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null])
Proud to be a Super User! | |
Hello @MattRTemcool @MaryAnne @omgull @desac @OttoChr
I opened an issue with microsoft support to investigate it, you can follow the issue in the link to know the latest update regarding this issue
https://community.fabric.microsoft.com/t5/Issues/The-OData-connector-failed-with-the-following-error...
Proud to be a Super User! | |
Hi, We had the same problem.
You can try to change
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, null),
to
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null])
Works. thx
Fixed it for me too.
Found more explained here:
Solved: The latest version of the connector no longer perm... - Microsoft Fabric Community
Same problem here. We dont use Gateways and the Desktop app works perfectly. Waiting for a solution...
Hi, I'm having the same error. We use the cloud version of BC, so no gateway setup. Would love to know what we need to alter to get the powerbi's back up.
Same problem here
Have exactly the same problem as of today. Have to be something general and not specific by user
Hi, I'm having the same error from yesterday. I posted on the forum and got some replies all the same due to BC tables and no error on desktop version.
If you're able to refresh successfully in pbi desktop then their might something wrong with your gateway setup. Try to make a new gateway and then try.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 56 | |
| 55 | |
| 37 | |
| 18 | |
| 14 |