What causes DF-Executor-ParameterParseError?

A data flow parameter typed as 'integer' or 'boolean' is passed a string value from the pipeline — for example, a trigger parameter that carries the text '2024-01-01' assigned to an integer parameter. A dynamic expression used in the data flow parameter mapping (`@formatDateTime(...)`) evaluates to a format or value incompatible with the parameter's declared type. A date/timestamp parameter receives a string in a format the data flow parser does not recognize — ADF data flow date parameters are strict about format strings. A parameter was declared in the data flow definition but its type was recently changed, and the upstream pipeline's parameter mapping still passes a value of the old type

How do I fix DF-Executor-ParameterParseError?

In the pipeline editor, click the data flow activity, open the 'Parameters' tab, and review each data flow parameter assignment — the error message identifies which parameter value could not be parsed.. Check that the parameter type matches the value being passed — for example, a data flow parameter typed as 'integer' will fail if the pipeline passes a string expression that contains non-numeric characters.. If the parameter is populated from a pipeline variable or another activity's output, use ADF's 'Debug' with 'Override parameters' to inspect the resolved value at runtime.. For date/timestamp parameters, ensure the format matches what the data flow expects — ADF date parameters are strict about format strings (e.g., 'yyyy-MM-dd').. If the parameter includes a dynamic expression (e.g., @formatDateTime(.)), validate the expression in the ADF expression builder before running the pipeline to catch format or escaping errors.

Medium severitydata flow

Power BI Refresh Error:
DF-Executor-ParameterParseError

What does this error mean?

A data flow parameter received a value that could not be parsed into the expected type. The value passed by the pipeline to the data flow — via a literal, expression, or pipeline variable — does not match the parameter's declared type or contains characters that the expression parser cannot handle.

Common causes

1A data flow parameter typed as 'integer' or 'boolean' is passed a string value from the pipeline — for example, a trigger parameter that carries the text '2024-01-01' assigned to an integer parameter
2A dynamic expression used in the data flow parameter mapping (`@formatDateTime(...)`) evaluates to a format or value incompatible with the parameter's declared type
3A date/timestamp parameter receives a string in a format the data flow parser does not recognize — ADF data flow date parameters are strict about format strings
4A parameter was declared in the data flow definition but its type was recently changed, and the upstream pipeline's parameter mapping still passes a value of the old type

How to fix it

1In the pipeline editor, click the data flow activity, open the 'Parameters' tab, and review each data flow parameter assignment — the error message identifies which parameter value could not be parsed.
2Check that the parameter type matches the value being passed — for example, a data flow parameter typed as 'integer' will fail if the pipeline passes a string expression that contains non-numeric characters.
3If the parameter is populated from a pipeline variable or another activity's output, use ADF's 'Debug' with 'Override parameters' to inspect the resolved value at runtime.
4For date/timestamp parameters, ensure the format matches what the data flow expects — ADF date parameters are strict about format strings (e.g., 'yyyy-MM-dd').
5If the parameter includes a dynamic expression (e.g., @formatDateTime(.)), validate the expression in the ADF expression builder before running the pipeline to catch format or escaping errors.

Frequently asked questions

How do I find which parameter is causing the parse error?

The error message names the failing parameter. Open the data flow activity's 'Parameters' tab and review each mapping. For dynamic expressions, use the Preview button in the expression builder to evaluate the value.

What date format should I use when passing dates to data flow parameters?

Data flow date parameters expect ISO 8601: 'yyyy-MM-dd' for date and 'yyyy-MM-dd HH:mm:ss' for timestamp. Use `@formatDateTime(pipeline().parameters.runDate, 'yyyy-MM-dd')` when passing from a pipeline expression.

The pipeline parameter type matches the data flow parameter type — why does parsing still fail?

Type matching is necessary but not sufficient — the value must be valid for the type. A 'string' parameter still causes ParameterParseError if it contains unescaped quotes or brackets that break the expression parser.

Will downstream Power BI datasets be affected?

Yes — the data flow fails before processing any data. Dependent datasets and reports serve stale figures until the parameter value issue is resolved.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide