Skip to end of metadata
Go to start of metadata

Problem

Sometimes you will find a warning like this in the configuration import trace:

Unmet pre-condition: Field Entry in screen <Custom Field Key>:<Field Name> must exist

Solution

This error is stating that a field which exists in the source instance and that is provided in a plugin cannot be created in the target instance which is being imported into as the field does not exist in the target instance.

In order to work around this error, you should ensure that the plugin mentioned in the error with the <Custom Field Key>  is installed in the target instance with the same version that it had in the source instance and that the field mentioned in the error is created in the target instance before re-running the import.