How do customizations affect the import process?
If your deployment has customizations (such as specialized document types), errors integrating the customizations can often be a cause of the errors that occur during the validation phase of an import.
The following table summarizes how customizations can cause errors during an import:
| Scenario | Description | Possible errors |
|---|---|---|
| No customizations | Your deployment uses the default document types and DTDs that are supplied by IXIASOFT. | Few or no errors related to the configuration. Errors during the validation process are most likely because the imported files are invalid. |
| Customizations | Your deployment uses customized DTDs and/or specializations. | There could be errors in the configuration. The Import Errors dialog should point to possible files where the errors are. Otherwise, the best files and folders to check for errors are:
|
| New and legacy customization | Your deployment uses customized DTDs and/or specializations. Some of these customizations are for your current content, but other customizations are for legacy content that you want to preserve or maintain. | There could be errors in the configuration. These errors could be for your
current customizations, related to the legacy customizations, or be a result of
conflicts in the configuration of your customizations. The Import Errors dialog should point to possible files where the errors are. Otherwise, the best files and folders to check for errors are:
|