# Resolving Custom Field Conflicts

Whenever you import something which has Custom Fields, you will be presented with a conflict resolution panel unless all of the custom field definitions in the import file already exactly exist. When there are differences, the current and import values, (when applicable), will be displayed. Values which differ are highlighted in red.

There are five types of conflicts which can be displayed:

1. The imported custom field is an entirely new custom field without conflicts. There are no current values to display.
2. The imported custom field is a new custom field with mapping conflicts. At least one of the low level mappings are already used elsewhere. There are no current values to display. If you choose to proceed, the conflicting mappings will be renamed to unique values. These can be modified later in Preferences-General-Custom Fields
3. The custom field's mappings exactly match those of a single existing custom field but the name differs. The current values will be retained. You can rename a custom field in Preferences-General-Custom Fields.
4. The custom field already exists and has at least one different setting. You can keep the current values or choose the import values.
5. The custom field already exists. At least one of the low level mappings is already used elsewhere. In this case the current values will be preserved.

Before choosing the current or import values you can check the For all items on this type setting. If you do this, all items of the same type will be resolved with your choice.

When you resolve a conflict or accept a new mapping the other Yate constructs being imported are resolved accordingly.