Forum Discussion
DataFlow possible bug?
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;
- Used the Merge Queries as New option rather than Merge Queries.
- Have the dataflow table load into memory by checking Enable Load option within Power Query Editor.
- Rebuilt the Dataflows.
- Rebuilt the report in the latest version of PBI Desktop (2.67.5404.981 64-bit (March 2019)).
- Confirmed the gateway is on the latest version (3000.2.52 (march 2019 release 2)).
- Removed the merge (obviously this works but is an unacceptable solution as I need that data merged).
- Re-entered credentials for the dataflow in PBI Desktop and on the Service.
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
- majdkaid227 years agoHelper V
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
- mark_carlisle7 years agoAdvocate IV
majdkaid22 Any luck with MS on resolving the issue?
- Anonymous7 years agoNot applicable
I had the same issue while taking data source from dataflows. Update Gateway and the problem is resolved.
- majdkaid227 years agoHelper V
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...