Metadata Import Errors
Errors that occur when attempting to apply metadata from the metadata import are logged in the job log file. Below is a list of metadata errors that can occur and an explanation of the cause of each error. This will help you correct the issue for subsequent job runs.
Error | Description | Cause |
|---|---|---|
AttributeDataImportFailed | The record could not be imported due to an unknown failure. {0} The given instance violated a constraint. | This exception occurs when the metadata value is too long. Review the metadata values in the import file and adjust any that conflict with metadata value lengths on the destination. |
AttributeDataImportDestinationNotMapped | The mapped source does not exist or was not transferred successfully to the destination. | This exception occurs when the source path is left blank in the import file. This exception always occurs with the AttributeDataImportSourceNotMapped exception since no action can take place on the destination without the source file path. Review the import file and make sure a path is provided for every entry. |
AttributeDataImportSourceNotMapped | The source path could not be determined from the input values. | This exception occurs when the source path is left blank in the import file. An invalid path of file name will also end up causing an AttributeDataImportDestinationNotMapped exception. Review the import file and make sure a path is provided for every entry. |
MetadataImportNoProperties | The import file did not contain any mappable metadata property fields. | This exception occurs when the metadata map contains a valid file path but doesn’t contain any mappable fields. No metadata has been added to the import file. Add at least one metadata field to the import file. |
MetadataImportUnknownProperty | There was an unexpected property contained in the import file: '{0}' | This exception occurs when there is a mapping field name in the import file that does not exist on the destination. This can occur along with the MetadataImportNoProperties error if all the field names in the file don't exist on the destination. Review the field names in the import file and adjust them to match the corresponding metadata field names on the destination. |
MetadataImportSourceMappedToContainer | The source path cannot be used because it was mapped to a directory. | This exception occurs if a path in the import file maps to a folder instead of a file. Review the paths in the import file and edit them as needed to point to the proper file location. |