There are two main types of errors that can occur when importing Web Client profiles and search forms:
Fatal errors that prevent the entire profile/search form from being created at all.
For example, a fatal error would occur if the import file had been edited and was no longer in a valid format.
Exceptions that don’t stop the profile/search form from being created, but cause it to not necessarily reflect the original exported version.
For example, an exception would occur if the import file included a reference to an additional field that doesn’t exist.
If the import successfully created any profiles or search forms, then any errors that occurred during the import are displayed in a dialog box after the import. The same information is also saved in text file in the Import_Export directory on the application server. The log file uses the same name as the import file with the extension .LOG.
The following table lists the exceptions that can occur when importing Web Client profiles and search forms. In this case, the profile or search form will still be added, but information might be missing. You can edit the profile/search form to correct the problem.
| Code | Error | Description |
|---|---|---|
| Exceptions for Profiles | ||
| 500 | Additional field ‘<name>’ not found. | The profile contains a reference to an additional field that doesn’t exist. This happens if the field was deleted after you exported the profile or if the field was created on one environment and you are importing into a different environment. The profile will still be added. You can edit it manually to add back any missing additional fields. |
| 501 | Folder with ID ‘<ID value>’ not found for notes. | The profile contains a reference to folder-specific notes for a folder that doesn’t exist. This happens if the folder was deleted after you exported the profile or if the folder was created on one environment and you are importing into a different environment. The profile will still be added. You can edit it manually to add back any missing items. |
| 502 | Contact Type with ID ‘<ID value>’ not found for criteria. | The profile used the specified contact type as the criteria for determining which contacts have the profile. The contact type does not exist. This happens if the contact type was deleted after you exported the profile or if the contact type was created on one environment and you are importing into a different environment. |
| Exceptions for Search Forms | ||
| 600 | Additional field ‘<name>’ not found for search. | The search form contains a reference to an additional field that doesn’t exist. This happens if the field was deleted after you exported the search form if the field was created on one environment and you are importing into a different environment. The search form will still be added. You can edit it manually to add back any missing additional fields. |
| 601 | Folder with ID ‘<ID value>’ not found for search criteria. | The search form contains a folder inclusion search criteria item for a folder that doesn’t exist. This happens if the folder was deleted after you exported the search form or if the field folder created on one environment and you are importing into a different environment. The search form will still be added. You can edit it manually to add back any missing items. |
| 602 | Contact Type with ID ‘<ID value>’ not found for search criteria. | The search form used the specified contact type as the criteria. The contact type does not exist. This happens if the contact type was deleted after you exported the search form or if the contact type was created on one environment and you are importing into a different environment. |