Let’s suppose you have a CSV file (CSV1) with the following columns:
and you have a configuration mapping (CM1) associated to the above CSV file with all cell mappings for each column (eg: a1 value in column A mapped with A1 on testrail, c1 value in column C mapped with C1 on testrail and so on).
If you reorder the CSV file columns (eg: A,B,C -> B,C,A) the configuration mapping CM1 is not more usable because you’ll get wrong mapping cell values (eg: c1 -> A1 on column 1). It seems that the configuration mappings work as positional mapping and ignores column names.
- using column names as keys, we could be able to use the same configuration mapping even if imported CSV has a different column order (but same column names).