CMS Request: Automatically Deselect Unmapped Columns When Importing Collections
Collecting votes
Currently, when importing collection content from a CSV file, all columns from the source file are automatically selected by default. This includes previously unmapped columns, which are treated as new collection fields, requiring users to manually deselect them to avoid clutter or unintended additions.
This feature would allow you to automatically deselect unmapped columns from the source file, so you can focus on mapping only the relevant columns. For example, when re-importing data from a prior session, unmapped columns (left out in the initial import) would remain deselected by default.
We are always working to update and improve our products, and your feedback is greatly appreciated.