You are here: System administration > Importing and exporting > Importing specifications

Importing specifications

You can export selected specifications to a .dox file, and import specifications into the database. The import/export function provides valuable information about the versions of the specification and any conflicts that arise. Using this information, you select which specifications to import/export and see which dependent specifications are included.

To import specifications in a file to the database

  1. On the Configuration tab of the Administration module, select Configuration > Import. The Import specifications dialog is displayed.

  2. Click Browse and select a .dox file to import from.

  3. The Select specifications to import table is divided into four sections and displays information on the specifications in the database versus those found in the .dox file:

    • Specification name, ClosedType of specification and if the specification is Built-in.

      In the Type column, both field templates and classifier templates are labeled as "Field templates".

      If you have a solution with a lot of classifier templates, and need to find your classifier templates more easily, name all your classifier templates with the same prefix, for example:

      • ClassTemp - Document A

      • ClassTemp - Document B, etc.

      Then, in Import/Export, sort by Specification name, and all your classifier templates will be grouped together under ClassTemp.

       

    • Database version created, Database version modified, and Database version: applies to the specifications in the database.

    • File version created, File version modified, and File version: applies to the specifications in the .dox file.

    • Merge conflict and Merge action compare the database and .dox file and list the action that is taken when you click Import.

    Consult the table, comparing the specification in the database with the one in the file, taking into account any ClosedMerge conflicts.

    • None – the specification does not exist in the database.

    • ID – an identical specification already exists in the database.

    • Name – another specification with the same name already exists in the database.

    Normally, the most suitable resolution (ClosedMerge action) is selected by default. However, in most cases you can click an action and change it, if needed.

    • Add – adds the specification to the database.

    • Keep – preserves the specification in the database because it is newer than the version in the file.

    • Replace –  replaces the specification in the database with the newer version from the file.

    • Rename – names the imported version of the specification "Copy of <OriginalName>". If the database already contains a specification with this name, the new copy it is named "Copy(2) of  <OriginalName>", etc. This renaming occurs automatically, but ideally you should give them a meaningful name after importing.

  4. Select a specification by clicking anywhere in the row. Any specifications required by the specification you selected, appear in the ClosedDependent specifications table.

    All dependent specifications, which are automatically included during import, are displayed here. Those that are also found in the Specifications to import table are bolded and italicized. You cannot deselect dependent specifications.

  5. If you selected one or more solution specifications, select Include sample documents below the table to import all sample documents found in the solution(s).

  6. Select Import at the end of a row. This specification is bolded. Other specifications required are italicized. The number of selected and total specifications included for import are displayed.

  7. Repeat step 4–6 for each specification you want to import.

  8. Create a backup fileis selected by default. This creates a backup copy (a .dxb file) of your configuration database before importing the new specifications (the same as if you had followed the procedure in Backing up the configuration database). This file is saved to the location from which the .dox file is fetched. If you do not want that backup file, deselect Create a backup file.

  9. Click Import.

Examples

 

Exporting specifications

Managing conflicts between a specification to be imported/exported and an existing one

Import and Export: Overview

Backing up a database

Restoring a database