#35. Azure Data Factory - Fix Mapping Column issue in Mapping Data Flow

In the pipeline, if we have a mapping data flow pointing to an excel file, it will have a set of columns defined as part of schema. If we change that file or create a new source, sometimes, you will end up seeing the total columns brought by the excel source to be 0. If it is the case, you will not be able to use the source in the data flow. This video explains a simple trick to refresh the schema and make the data flow work for you, Please watch it and let me know your comments.

[SantoshSingh-kibx]

Life saver. This is the issue I was facing till date. Thanks for sharing such a good content

[vlogwithdevesh]

This issue came after deriving some columns and was kind of stuck why the columns are not showing.. then I refreshed the whole adf page for this anyways that is the easier technique.
Thanks>>

[stephenmartin]

How would you handle an instance where a text file containing a header is received from a vendor
Column1|Column2
Your data flow handles that no problem.
A second vendor sends you the same file but their column headers are of a different case:
COLUMN1|Column2
This breaks your data flow as the schema derived from the original vendor no longer matches the 2nd vendors file.
How would you handle this?
A Python batch service pre-processor .. or can a data flow deal with this?
Thanks Stephen

[bitasam]

in sink when i try to do manual mapping the column name i get is wrong and i cannot change it as it has only select option no write option and no of column is also wrong how can i fix it

[ajay_jangra]

Thanks Mam, I was facing exactly the same issue :)