Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hello community,
I have my data source as MS business central. When I refresh on desktop, it works fine without any errors. However, when scheduled refresh or manual refresh online, it returns the below error.
Data source error: 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: LotNoInformationList.
Cluster URI: WABI-UK-SOUTH-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 50d92772-e7ba-4953-8dd1-dd60c4ec3044
Request ID: d9f0b6f9-b3c6-1882-5d96-93f34fb03110
Time: 2024-09-03 15:35:47Z
Similar error on all my reports with various datasets. This triggered today morning onwards.
I did try to remove the 'null' from the dataset, but still the error persists.
Any tips on how to resolve it?
Many thanks.
Solved! Go to Solution.
The latest version of the connector no longer permits the 4th parameter to be null.
Please try the following solution:
Before:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, null)
After:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null])
The punctuation is also standard for error messages.
Microsoft supposedly rolled out a fix yesterday but I am still getting an error when trying to connect to the Business Central API. Note: This is not for an existing file where I can edit the URL. This is for a NEW connection so I am currently stuffed.
Any suggested solutions?
https://support.fabric.microsoft.com/en-US/support/
Not sure if you found a fix, I also was recieving that error for my Biz Central connections. In Power Query I clicked the "Go To Error" button then clicked "Edit Settings" the next window that pops up gives you 'Optional' places to enter data. I left them all blank, just click ok & the connect went through; I was able to save & apply, then refresh my data afterwards. Hope this helps.
Did you get this solved? I also have a user in my org that is having this issue.
I did not have to downgrade my desktop version. Go into Power Query in "Transform Data". Click on the go to error button on the table, then click edit settings. A new window will appear allowing you to enter 'optional' information. Leave it blank, just click OK. This re-established my connection like normal & was able to refresh my data.
Yeah, downgrading the desktop app to the old version sorted the problem out. You have to manually download it off Microsoft website, uninstall current version and then install the old version. Connected to API perfectly.
I am new to Power BI. Does anyone have a SOP to show how to apply the fix?
The latest version of the connector no longer permits the 4th parameter to be null.
Please try the following solution:
Before:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, null)
After:
Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null])
In your powerbi desktop report > Transform data > select and highlight your Business Central related query > open Advanced editor > replace the first line as described above > Ok > Close & Apply once updated to all BC related queries
This fixed my issue in Power BI Desktop, thank you!
But now when I upload it to my Power BI dashboard and run it, it bombs out still. Any ideas?
I could recommend reviewing that "Table: Outstanding_Sales_Order_Status_Excel." query line-by-line in the advanced editor for a similar line to edit. If not found (assuming the data source is an excel) you may need to open the sheet and explore the power query editor there. Open sheet > Data > Get Data > Launch Power Query Editor
I'm trying to publish a PBIX from the desktop with the fix applied "[UseReadOnlyReplica = null]", however I'm getting this error...
ServerError_CloudStorageBlobStorageServerException
when I force a manual refresh in the Power BI Service after the publish. Any suggestions?
I changed "[UseReadOnlyReplica = null]" to "[UseReadOnlyReplica = true]" and was able to get pass that error.
I used this solution and it fixed my issue. Do u think these two [UseReadOnlyReplica = null]" to "[UseReadOnlyReplica = true] can result in different outputs.
Hi @Aditi_ , I believe the default value of UseReadOnlyReplica is true; therefore the 'null' or 'true' will result in the same data refresh performance.
That worked. Thank you!
Ahh thank you so much! Same issue here. Spent several hours today trying to fix this. Would be great if the troubleshooting messages in PowerBI were a bit more precise..
Thanks Dejan-Pajk,
That fixed it for me too...
This work around fixed it for me too, many thanks for your assistance.
Greatly appreciated.... off to rework 35 reports too now 😞
Glad it worked. Are you changing it manually for all queries?