Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!

DataFormat.Error: There were more columns in the result than expected..

DataFormat.Error: There were more columns in the result than expected.. Microsoft.Data.Mashup.ErrorCode = 10216. Count = 7. ;There were more columns in the result than expected.. The exception was raised by the IDbCommand interface.

 

this error show yesterday afternoon when i tried to refresh my report (2 different report with 2 different BC licenses). Before that, i refreshed it twice, and it worked. 

Status: New
Comments
threecoffees
New Member
I am also getting the same error. Supposedly it's a wide spread issue with the Business Central/Power BI connector. It has been going on for over 24 hours now.
cheryllee
New Member
Same here. The same error occurred in my reports about 12 hours ago. It was working fine yesterday. Could it be due to a Microsoft update somehow?
threecoffees
New Member
It looks Microsoft related. See below post on the Business Central forum. A poster suggests that the workaround is to either use an OData/API feed until Microsoft sort the issue out. However, that means you'd have to reconfigure your reports and re-publish. https://community.dynamics.com/forums/thread/details/?threadid=45c2c22e-0bc5-f011-bbd3-000d3a110039
tejaswi_464
Regular Visitor
Users also experiencing the same error Supposedly it's a wide spread issue with the Business Central/Power BI connector. It has been going on for over 24 hours now. It's impact the customer refreshes and productivity
Felisia
Regular Visitor
it seems already back to normal? i already change some of the source through OData though, it worked yesterday, today i try to refresh some of the source, that i hadn't change into Odata, and they also work fine. Does the problem solve? Should i change back the source through BC connector? or just leave it with Odata? Any suggestion? 
tejaswi_464
Regular Visitor
Hello @Felisia, You can revert to BC connector . BC connector is working now