Import Restrictions

Learn about the import restrictions applied.

The following restrictions apply:

  • The SU and WWW users' passwords are not imported.
  • Packages can only be imported on a station that is set up as the main office (in the Station info area).
  • The Main Office field is ignored when importing stations on the target database (i.e. the main office is left unchanged by the import).
  • The package ID defined in the Settings.xml file (CustomerInstanceID element) on the source and target stations must match. If no ID was assigned to the package on the source station, the package can be imported on any station (even if an ID is defined in the Settings.xml file on the target station).
  • Apart from base packages (see Base Packages ), packages can only be imported into databases of the same version of Aurea.CRM (same vertical and service pack). Base packages can be imported into any vertical of the same service pack.
  • Packages can only be imported by the SU.
  • The catalog base language number must be identical on both the source and target stations.
  • Only global formats in triggers can be imported. Ensure that all such formats are global, not private.
  • Private automatic selection and project selection formats are always added for the user that imports the package (SU), not the original user.
  • The predecessor activity referenced by its follow-up activities is not automatically added to the packages although the reference is imported; an incorrect activity record may be referenced as a result.
  • In order to import sample records (OTC), you need to define two processes. The first process you define should contain the sample codes (MK) and additional rep info (AZ) relating to the sample record. The sample record (MU) itself should be added to a second process, which must be defined after the first process.
  • The "UPDATE_DEFAULT" configuration must be present in the designer database. This configuration is never included in packages.
  • The station numbers of the source and target stations must be different in order for the data model to be imported and merged. The data model is merged in the same manner as data models are merged in Aurea.CRM win. For more details on merging data models, >> Merging Data Models in the CRM.core Administrator Guide.
  • If the source station is assigned a base station number (10,000 and 10,010-10014), only packages exported on a base station can be imported.
  • The values in the External Key, Lock and Sort Order fields of imported catalog values are not displayed in the details view until the application is restarted.