Can I change a configuration's mapping later?
Yes. Saving the mapping makes a new version; the next upload uses it, and a file in review can be checked again with it. Published items change only when a file says so.
- 1 min read
- Updated October 14, 2026
Yes. Edit configuration opens the same editor, and Save makes a new version. The next upload uses the newest version; a file that is already in review shows Check again with version N to use it. Items already on your site are untouched until a file publishes them.
Expect the first file after a change to ask for your confirmation. A mapping change shows in the review only where it changes what would be sent: the review lists exactly what changes. A field you switch to Keep existing on updates is simply no longer sent, so by itself that changes nothing on the site.
Edit a configuration and its versions explains what each version keeps.
Was this article helpful?
Related articles
- Importing dataEdit a configuration and how versions workChange a mapping safely: each save makes a version, files keep the version they were checked with, a new version can be applied to a waiting file, and conflicts are flagged.
- Importing dataWhen a file's columns changeWhat "This file doesn't match the configuration" means, which columns count as used, how to rename a column back or remap it, and what new or removed columns do to the review.
- Mapping columnsValue modes: column, fixed value, template, default, keep, removeThe six ways a field gets its value, and what each does when an item is created and when it is updated: column, fixed value, template, default, keep existing, remove.