What causes UserErrorColumnNotFound?

A column referenced in a copy activity mapping no longer exists in the source or sink. A derived column, filter, or aggregate expression references a field by a name that was renamed upstream. The data flow was built against an older snapshot of the schema and the source has since changed. Case sensitivity mismatch between the column name in the expression and the actual schema

How do I fix UserErrorColumnNotFound?

Re-import the source schema in the dataset or data flow to detect the current column list.. Search all activities in the pipeline for references to the missing column name.. Update or remove mappings, expressions, and filters that reference the old column name.. If the column was renamed in the source, either rename it back or update all downstream references.. Use debug mode in data flows to see the live schema at each transformation step.

High severityconfiguration

Power BI Refresh Error:
UserErrorColumnNotFound

What does this error mean?

ADF could not locate a column referenced in your pipeline's mapping, filter, or expression — it does not exist in the current schema or was renamed since the mapping was last saved.

Common causes

1A column referenced in a copy activity mapping no longer exists in the source or sink
2A derived column, filter, or aggregate expression references a field by a name that was renamed upstream
3The data flow was built against an older snapshot of the schema and the source has since changed
4Case sensitivity mismatch between the column name in the expression and the actual schema

How to fix it

1Re-import the source schema in the dataset or data flow to detect the current column list.
2Search all activities in the pipeline for references to the missing column name.
3Update or remove mappings, expressions, and filters that reference the old column name.
4If the column was renamed in the source, either rename it back or update all downstream references.
5Use debug mode in data flows to see the live schema at each transformation step.

Frequently asked questions

Why did this error appear suddenly without any change on my side?

A schema change on the source side — such as a DBA renaming a column or a source team updating an API response — can trigger this error in a previously working pipeline.

Official documentation: azure-data-factory