Skip to end of banner
Go to start of banner

Resolve Custom Field Conflicts

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


How to resolve custom field conflicts?

If Duplicate Custom Fields are detected, you'll be presented with a page where you can resolve the conflicts.

For each duplicate field, there is a separate expandable section distinguished by the name and type of the field. In each section, there is a mapping table - on the left, you see all the fields with that name and type from the snapshot and on the right, you have a drop-down where you can select either one of the possible fields on the current target system (that has the same name and type) or you can choose to create a new field.

Custom fields are pre-mapped if they have the same native ID in the snapshot and on the target. Otherwise, the option to create a new field is selected by default - this way even if the user doesn't pay attention to this screen no existing data will be harmed and only new fields will be created.

  • No labels