Forum Discussion
1 arguments were passed to a function which expects between 2 and 3
Good Morning All,
I have a dataflow which gives me this error. The dataflow will work fine for weeks and then stop working with this error:
Error: Encountered user gateway exception: '<ccon>1 arguments were passed to a function which expects between 2 and 3.</ccon> [DM_ErrorDetailNameCode_UnderlyingErrorCode]=-2147467259 [DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>1 arguments were passed to a function which expects between 2 and 3.</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.ErrorCode]=10067
The rest of the error can be seen in this spoiler but it just repeats itself
But in reality, its the most simple code in the world: Please advise. My "FakeName" is another dataflow which runs just fine.
let
Source = PowerPlatform.Dataflows([EnableFolding = true]),
#"Navigation 1" = Source{[Id = "Workspaces"]}[Data],
#"Navigation 2" = #"Navigation 1"{[workspaceId = "3xxxxxxx-cxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
#"Navigation 3" = #"Navigation 2"{[dataflowId = "4xxxxxxx-cxxx-xxxx-xxxx-xxxxxxxxxxxx"]}[Data],
#"Navigation 4" = #"Navigation 3"{[entity = "FakeName", version = ""]}[Data],
#"Sorted rows" = Table.Sort(#"Navigation 4", {{"INDEX_ID", Order.Ascending}})
in
#"Sorted rows"Please advise. My "FakeName" is another dataflow which runs just fine.
Hi BugmanJ,
Here looks like the error is from the gateway or the Power Platform Dataflows connector. Your code looks fine and this issue happens intermittently when the connector or gateway gets an incomplete or invalid response response from the power platform service. Please follow below steps:
- In your dataflow, remove the [EnableFolding = true] part and use this instead:
Source = PowerPlatform.Dataflows(null) - Save and refresh the dataflow again.
- If it still fails with the same error, then it is a transient gateway or service glitch. So just restart the gateway service or refresh again later, it will start working once the service returns valid data.
Thanks and regards,
Anjan Kumar Chippa
- In your dataflow, remove the [EnableFolding = true] part and use this instead:
6 Replies
It's probably not an issue, but what's the purpose of the '[EnableFolding = true]'?
As far as I'm aware, the typical statement is 'PowerPlatform.Dataflows(null)'.
Is there a gateway involved further upstream?
'GatewayClientErrorResponseException[GatewayId=1408102]'
Maybe check the gateway logs for any clues.
[quote]It's probably not an issue, but what's the purpose of the '[EnableFolding = true]'? As far as I'm aware, the typical statement is 'PowerPlatform.Dataflows(null)'.[/quote]
Correct, but it won't take (null) and enablefolding=true is the only parameter it will take.Going with a gateway error
Hi BugmanJ,
Here looks like the error is from the gateway or the Power Platform Dataflows connector. Your code looks fine and this issue happens intermittently when the connector or gateway gets an incomplete or invalid response response from the power platform service. Please follow below steps:
- In your dataflow, remove the [EnableFolding = true] part and use this instead:
Source = PowerPlatform.Dataflows(null) - Save and refresh the dataflow again.
- If it still fails with the same error, then it is a transient gateway or service glitch. So just restart the gateway service or refresh again later, it will start working once the service returns valid data.
Thanks and regards,
Anjan Kumar Chippa
- In your dataflow, remove the [EnableFolding = true] part and use this instead:
Hi BugmanJ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you KNP for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi BugmanJ
As per my understanding the error occurs because the referenced dataflow (“FakeName”) likely changes over time, such as a column rename or schema update, causing your dependent dataflow to break even though the code looks fine. It’s not a syntax issue but a schema or dependency mismatch. To fix it, reselect the “FakeName” entity in Power Query, verify columns match, and consider disabling query folding or specifying the entity version for stability.
