What causes DF-Executor-ColumnNotFound?

A column referenced in a Derived Column, Filter, or Join expression does not exist in the source schema — the column was renamed or removed. Schema drift is disabled on the source transformation, and the source removed a column that the data flow still expects. A column name is misspelled or uses different casing — ADF data flow column names are case-sensitive. The source projection was imported at a different time when the column existed, and has not been refreshed since the column was dropped

How do I fix DF-Executor-ColumnNotFound?

Open the failing transformation in ADF Studio and check the column name referenced — confirm its exact case and spelling against the source schema.. If schema drift is disabled on the source transformation, enable it: go to the source Settings tab and turn on 'Allow schema drift'.. Click 'Import projection' on the source transformation to re-import the current column list from the source.. If a column was recently renamed in the source, update all derived column, select, or filter expressions that reference the old name.. Enable debug mode and preview the source data to see the exact column names available at runtime.

Medium severitydata flow

Power BI Refresh Error:
DF-Executor-ColumnNotFound

What does this error mean?

The data flow references a column by name that does not exist in the incoming data stream. The column may have been renamed or removed in the source, the source schema was refreshed and dropped the column, or the column name in the transformation expression is misspelled.

Common causes

1A column referenced in a Derived Column, Filter, or Join expression does not exist in the source schema — the column was renamed or removed
2Schema drift is disabled on the source transformation, and the source removed a column that the data flow still expects
3A column name is misspelled or uses different casing — ADF data flow column names are case-sensitive
4The source projection was imported at a different time when the column existed, and has not been refreshed since the column was dropped

How to fix it

1Open the failing transformation in ADF Studio and check the column name referenced — confirm its exact case and spelling against the source schema.
2If schema drift is disabled on the source transformation, enable it: go to the source Settings tab and turn on 'Allow schema drift'.
3Click 'Import projection' on the source transformation to re-import the current column list from the source.
4If a column was recently renamed in the source, update all derived column, select, or filter expressions that reference the old name.
5Enable debug mode and preview the source data to see the exact column names available at runtime.

Frequently asked questions

How do I find which transformation references the missing column?

The error message includes the missing column name. In ADF Studio, use Ctrl+F to search for it across all transformations, or check each Derived Column, Filter, Join, and Select manually.

What is schema drift and should I enable it to prevent this error?

Schema drift lets new columns pass through — it prevents ColumnNotFound for added columns. It does not help when a referenced column is removed; delete the expression that references the missing column.

Why is the column name case-sensitive in ADF data flows?

ADF Mapping Data Flows run on Apache Spark, which is case-sensitive for column names. 'CustomerID' and 'customerid' are different columns — always use the exact case from the source schema.

Will downstream Power BI datasets be affected?

Yes — the pipeline fails on every run. Dependent datasets serve stale figures until the column reference is fixed.

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