Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi Community,
Am getting an error that I have not encountered before.
"The columns parameter must be null, specify the number of columns, specify a list of column names, or specify a table type."
After digging, I found out the cause. I have a mapping table in DataFlow, which am merging with other tables coming (non-DataFlow) in the PBI desktop Dataset.
Up until last last week, everything was working smooth, and no refresh interupttion, and then the above error started coming up.
I copied the mapping table code from the advance editor from DataFlow and put it inside PBI Desktop Dataset, and the error disappeared.
The issue seems to be tied up with the service/DataFlow
Anyone has encountered such error? what can be done to fix such error?
Thanks,
Majd
I had to install the april version of the Gateway to resolve this.
I had this bug for months and now after updating the gateway to the 2019-04-09 version it now works.
Same here. Thanks for all your help!
I'm also having this exact error. This error started to manifest itself on 05 April 2019 for me. This is occouring on multiple reports and can be created on demand.
I have attempted the following in trying to resolve;
Error as taken from PBI Service;
Something went wrong Unable to connect to the data source undefined. Please try again later or contact support. If you contact support, please provide these details. Underlying error code: -2147467259 Table: NonVoice. Underlying error message: The columns parameter must be null, specify the number of columns, specify a list of column names, or specify a table type. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: Expression.Error Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net Activity ID: 83703c77-276c-43e1-83ef-9790ea382b48 Request ID: ae46f037-b1dd-9558-316e-b59540007abf Time: 2019-04-08 09:40:59Z
@mark_carlisle Sorry for not responding back on time. FYI, similar issue happened yesterday and the Gateway July-2019 release 2 fixed the problem. in case you got the error you way...
@Anonymous @mark_carlisle
Microsoft Support team have confirmed this is a bug according to a reply on a support team I've opened. Am supposed to get into remote session with them to evaluate the issue.
I will update this thread as soon as I get further information
I had the same issue while taking data source from dataflows. Update Gateway and the problem is resolved.
I am on the March R2 right now and have no issue to refresh the report.
After digging, I found out the cause. I have a mapping table in DataFlow, which am merging with other tables coming (non-DataFlow) in the PBI desktop Dataset.
Up until last last week, everything was working smooth, and no refresh interupttion, and then the above error started coming up.
I copied the mapping table code from the advance editor from DataFlow and put it inside PBI Desktop Dataset, and the error disappeared.
Have you removed the dataset which is not created by dataflow? If you have, does this issue still exist in power bi service?
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@v-yuta-msft any update on the this issue please?
Am getting same error on other reports as well. Any merging or Appending in PBI desktop between table stored in DataFlow and other tables from other sources is causing the problem on PBI service only
I am getting the same issue across several of my dataflows now. If I run the sql query inside the dataflow it works but any reference to dataflows outside of that workspace has stopped working all of the sudden! I'm not sure how to even workaround this issue without undoing all my work. If this isn't a bug, can someone put me on the right path of what it might be please?
Thanks,
Scott