Dataflow Gen2 (CI/CD) Data Pipeline Activity Fails when Dynamic Parameters Passed from Data Pipeline

Question

Hi Fellow Fabricators,&nbsp;This one gave me a nasty headache, so I'm posting here to help others with the same issue.&nbsp;Error code:&nbsp;20302Failure type:&nbsp;User configuration issueDetails&nbsp;Dataflow refresh job failed with status: Failed. Failure reason: { requestId: [guid], errorCode: 105004, message: . Learn more at https://go.microsoft.com/fwlink/?linkid=2314100 }Error Link:&nbsp;Troubleshoot connectors - Microsoft Fabric | Microsoft Learn&nbsp;The error code Troubleshoot guide is generic and the failure reason message is missing.&nbsp;High-level config details&nbsp;DataflowGen2 (CI/CD):public parameters mode enabledruns successfully when (using "current value" in parameters)executed manually (save, run &amp; close)refreshed (manually) from UIrun fails&nbsp;when called from a dataflow activity in a data pipeline, andpipeline passes 3&nbsp;dynamic&nbsp;parameters into dataflow&nbsp;MICROSOFT RESOURCESDataflow Gen2 CI/CD - in GA May 2025Deployment&nbsp;Pipeline Parameters are supportedData Pipelines:&nbsp;Dataflow Activity supports&nbsp;Dataflow Gen2 CI/CD&nbsp;Passing parameters into a Dataflow Gen2 CI/CD from a Data Pipeline activity is supported: and referenced thus&nbsp;"When selecting a Dataflow Gen2 with CI/CD that has the public parameters mode enabled, a Dataflow parameters section is displayed which lists all the available parameters, their types, and default values for the selected Dataflow."&nbsp;&nbsp;SOLUTION&nbsp;After a lot of config tweaking to identify the root cause, it was a simple data typing issue (of course!!).&nbsp;Parameters in data pipeline items must be strongly typed - mine were of type [String]The DFG2 parameters were of type Any - this is usually really forgiving.&nbsp;By changing the data type of all parameters in DFG2 to [Text] the DPL activity ran perfectly.&nbsp;NOTES:&nbsp;The error could be much more meaningful - and indeed the documentation should be updated to make this data type match requirement clear.&nbsp;Dataflows and Data Pipelines have different development stories:Dataflows have evolved considerably since their origin in Excel Power Query (aka Data Explorer)Fabric data pipelines began life in Azure Data Factory - with some Azure Synapse pipeline DNA.It is clear that these Fabric items are still not fully consistent - not least because types String and Text are not interchangeable/identical at a technical level 😛

bettinaek · Accepted Answer

SOLUTION: Parameter data types must align in DFG2 &amp; DPL&nbsp;After a lot of config tweaking to identify the root cause, it was a simple data typing issue (of course!!).&nbsp;Parameters in data pipeline items must be strongly typed - mine were of type [String]The DFG2 parameters were of type Any - this is usually really forgiving.&nbsp;By changing the data type of all parameters in DFG2 to [Text] the DPL activity ran perfectly.&nbsp;NOTES:&nbsp;The error could be much more meaningful - and indeed the documentation should be updated to make this data type match requirement clear.&nbsp;Dataflows and Data Pipelines have different development stories:Dataflows have evolved considerably since their origin in Excel Power Query (aka Data Explorer)Fabric data pipelines began life in Azure Data Factory - with some Azure Synapse pipeline DNA.It is clear that these Fabric items are still not fully consistent - not least because types String and Text are not interchangeable/identical at a technical level : p

Forum Discussion

Dataflow Gen2 (CI/CD) Data Pipeline Activity Fails when Dynamic Parameters Passed from Data Pipeline

2 Replies

Related content

Parameters to fabric pipeline

Dataflow Activity Parameters Lose Expression and Get Hardcoded After Reopening Pipeline

Pipeline Schedule Parameters failing to run immediately.

Pipeline Parameters Reverting to Dataflow Defaults – How to Confirm Actual Applied Values?

Pass data pipeline parameter to dataflow gen2