Import Settings

Learn about the import XML files in CRM.cockpit.

The ImportConfigExample.xml file located in the CRM.cockpit root directory provides you with a simple template XML file for importing packages. You can create a copy of this file and adapt it to meet your needs.

The import XML file supports the following nodes:

DeployWebOfflineFiles

If set to true, web offline files (files containing the '$WEB' placeholder) are copied to Aurea.CRM web offline's global patch directory. This setting only applies if the package is flagged as containing web offline files (Contains web offline files option or PackageContainsWebOfflineFiles parameter in the export XML configuration file, >> Deploying Offline Files .

Note: Ensure that you have defined the path for the '$WEB' placeholder under FilePaths (see below).

ItemsToImport

The elements in this node define which items should be exported (similar to the ItemstoExport node in the export configuration XML file, see Export Settings ):

  • ItemsToImport\CoreItems

    Determines whether core items should be imported. The default value is true.

  • ItemsToImport\CatalogMaintenanceItems

    Determines whether catalog maintenance records should be imported. The default value is false.

  • ItemsToImport\TextTableItems

    Determines whether the contents of the Text info area should be imported. The default value is true.

  • ItemsToImport\DesignerUnits

    Determines whether designer units should be imported. The default value is true.

  • ItemsToImport\FieldHelp

    Determines whether the field help is imported. If field help is imported, all text table entries referenced by the field help are also imported, even if ItemsToImport\TextTableItems is set to false. The default value is false.

  • ItemsToImport\Files

    Determines whether files should be imported. The paths to be used by placeholders are defined in the FilePaths element. The default value is true.

FilePaths\Item

Each Item node contains a Key attribute, which corresponds to a placeholder used in file paths (e.g. "$WEB"). Define the associated file path for the placeholder in the Path element (e.g. "C:\web\").

UpdateCrmDesigner

These settings determine how catalogs in the CRM.designer database are updated by the import:

  • UpdateCrmDesigner\UpdateCatalogs

    Determines which catalog values are updated in the CRM.designer database. The following options are available:

    • NewOrChanged: Any catalogs values that are added or updated by the import process are synchronized with CRM.designer (default).
    • Existing: Only existing catalog values are updated by the import process and synchronized with CRM.designer. Determine how catalog values are matched up using the CatalogSyncMode element.
    • None: No catalogs are updated in the CRM.designer database.
  • UpdateCrmDesigner\CatalogSyncMode

    Determines how existing catalog values (Existing option in the UpdateCatalogs element) are matched up with catalog values in the package:

    • Text: Catalog values in the package are matched up with catalog values in the target CRM.designer database by the value in the catalog base language and tenant number (default).
    • ExternalKey: Catalog values in the package are matched up with catalog values in the target CRM.designer database using the catalog value's external key.