View and troubleshoot import jobs

You can view import job details as well as perform troubleshooting for jobs that encounter errors. 

View import jobs

You can view the completed and in-progress import jobs for a case on Imports pages. Jobs appear in reverse chronological order, and the jobs that you saved as drafts appear at the top of the list. You can also click an individual job to view its properties and errors.

Caution: You can modify a job only before you submit the job for processing.

The processing icons indicate the job status. Hover over the icon to view information about the status.

Note: A job without an icon in the first column is still a draft, and has yet to be scheduled or submitted. Draft jobs appear at the top of the list without start times.

To view import jobs, on the Case Home page, under Manage Documents, click Imports.

To view the properties of an import job, on the Imports page, click the name of a job.

To print the import properties, click Print, and then follow the on-screen instructions.

Note: If you or another user save the job as a draft, you can still edit the job options and settings. After you schedule the job, you can copy and paste this information into an email or a Microsoft Word document, or click Print.

Troubleshoot import jobs

You can view errors for an import job as well as view a table with common import exceptions and possible resolutions.

View errors for an import job

To view errors for a job:

On the Case Home page, under Manage Documents, click Imports.

On the Imports page, click the name of a job that failed or completed with warnings.

In the navigation pane, click Errors.

Note: Hover over the message in the Error column to view the entire error message.

Common import exceptions and possible resolutions

The following table provides common import exceptions, descriptions of the exceptions, and possible resolutions.

Exception

Description

Possible Resolution

Inventory Job failed.

You may receive this error message when you click Get fields on the Fields page in the Import window, if you have not selected the correct delimiters for your import, or if your load file has a formatting issue.

The load file may have a formatting issue. Check your load file. Or confirm the delimiter settings in your job. You can find these on the Delimiters page and the Field Map page in the Import window for value delimiters for one-to-many fields. If the delimiters are correct, you will then need to confirm that all of the delimiters in your load file match these settings.

Native file for this document does not exist.

You may receive this error message because the path in the load file does not match the path where the files actually exist, or because the native file does not exist at all.

Validate that the path in the load file is correct. If the path in the load file is correct, check the folder to make sure that the file actually exists.

Also ensure that you selected the same folder level for the native files on the Metadata File and Source File page in the Import window.

Metadata File page in the Imports window with a pointer to the Native folder.

Source File page in the Imports window with a pointer to the Native folder.

Host reference value of X was not found for the document ID Y.

You may receive this error if the parent document does not exist in the load file or the case.

Check the load file and ensure that the parent document ID is valid.

The import was aborted because a duplicate document was found.

If you selected the Abort import, if it contains an existing document ID option, shown in the following figure, in the Import action list on the Existing Documents page in the Import window, if it contains an existing document ID, it will do just that.

Select a different Import action on the Existing Documents page in the Import window if you are intending to do an overlay.

Otherwise, verify why you have overlapping DOCIDs and correct the issue.

The field defining the source and attachment relationship contains no values for any documents.

You may have selected the wrong field, or there may actually be no source and attachments.

On the Document ID page in the Import window, in the Source and Attachment relationship list, ensure that if you select Parent Doc ID that you also selected a field for the Parent Doc ID in the Field defining Source and Attachment relationship list.

Document ID page in the Import window with pointers to the Parent ID option in the Source and Attachment relationship list and to the "Field defining Source and Attachment" list.

If you selected Attachment Doc IDs or Family Range in the Source and Attachment relationship list, ensure that they match up with the right fields accordingly.

Error copying file "Imports\CM_Import\DOC-000000001.pdf" for document "DOC-000000001": Destination page file already exists.

On the Source Files page in the Import window, the user did not select the following check box to overwrite existing files: Overwrite matching source files and/or content files already on the server

On the Source Files page in the Import window, check the following option and rerun the import: Overwrite matching source and/or content files already on the server.

Overwrite matching source and/or content files already on the server option on the Source Files page in the Import window.

Or, if this was for a metadata-only overlay, then nothing needs to be done.

Could not interpret any metadata values in the first 200 rows of this page file. Import has been aborted.

There are legitimate delimiters in the load file, but some are missing.

You likely need to make corrections to your load file to make sure it is properly delimited.

Missing data in field MemoValue for the category 'MEMO' for Document_ID "{Document_ID}."

Nothing was in the load file for one of the MEMO fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

Missing data in field TheValue for the category 'BOOL' for Document_ID "{Document_ID}".

Nothing was in the load file for one of the YES/NO fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

Missing data in field TheValue for the category 'DATE' for Document_ID "{Document_ID}".

Nothing was in the load file for one of the DATE fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

Missing data in field TheValue for the category 'NUMB' for Document_ID "{Document_ID}".

Nothing was in the load file for one of the NUMBER fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

Missing data in field TheValue for the category 'PICK' for Document_ID "{Document_ID}".

Nothing was in the load file for one of the PICK LIST fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

Missing data in field TheValue for the category 'TEXT' for Document_ID "{Document_ID}".

Nothing was in the load file for one of the TEXT fields in your load file for this Document_ID.

If this was intentional, this is fine, and just a warning.

TheValue {theValue} is invalid for the category 'BOOL' for Document_ID "{Document_ID}". Valid values are: YES, NO, Y, N, 1, 0, True or False

Your load file has something other than a yes/no entry for one of the YES/NO fields in your load file for this Document_ID. Your document loaded, but this field for this document did not populate.

Update the values in your load file to conform to the requirements for the field; or update the field type to a type appropriate to the values.

TheValue {theValue} is invalid for the category 'NUMB' for Document_ID "{Document_ID}". Expected numeric value.Ref. Document_ID <DOCUMENT ID VALUE>.

Your load file has something other than a number entry for one of the NUMBER fields in your load file for this Document_ID. Your document loaded, but this field for this document did not populate.

Update the values in your load file to conform to the requirements for the field; or update the field type to a type appropriate to the values.

TheValue {theValue} is not in a valid date format for the category 'DATE' for Document_ID "{Document_ID}". Expected date format: 'dd-mmm-yyyy'.

Your load file has something other than a proper date format entry for one of the DATE fields in your load file for this Document_ID. Your document loaded, but this field for this document did not populate.

Update the values in your load file to conform to the requirements for the field; or update the field type to a type appropriate to the values.

The value is too long for Text field "{field name}" for Document ID "{Doc ID}". The maximum length is 255 characters. The value was not imported.

Your load file has something longer that 255 characters that it is trying to load into a TEXT field.

You may have forgotten a delimiter between multiple entries, you may have received an odd load file, or you may want to create a memo field instead.

The value is too long for Pick field "{field name}" for Document ID "{Doc ID}". The maximum length is 255 characters. The value was not imported.

Your load file has something longer that 255 characters that it is trying to load into a PICK LIST field.

Your load file has something longer that 255 characters that it is trying to load into a PICK LIST field.