Importing Model Elements

Elements of an existing model can be imported into other models. Developers can work simultaneously on the same model; importing the different elements to create a new model. You can also reuse parts of a model; streamlining your work and letting multiple developers work efficiently.

Settings and properties are not inherited from the source model. You can reconfigure them in the destination model if you want to keep the existing settings and properties.


  1. Open the destination model in the Design Tool.

    The destination model is the model that you will be importing to. It is a good idea to always backup your model before beginning the import process.

  2. From the File menu, choose Import Model Elements.

    The Import Model Elements dialog box display.

  3. Browse to the import model. You import from the source model(in dialog box) to the destination model, which is open in the Design Tool.

    The left pane displays a tree representation of the source model, including all entities, tables, and variables.

  4. Choose the elements of the model you want to import into the destination model.

    Model elements are those items that may be imported and comprise entities, attributes, operations, recordsets, recordset fields, tables, table columns, procedures and compound procedures, and model variables.

    When an operation containing a WaitForMultipleEvents command is imported, the referenced Host Events are also imported.

    Patterns and events cannot be imported separately from their entity.

  5. Preview your selected elements in the Import Action Preview pane. The preview pane is divided into insert elements, update elements, and referenced elements.


    • Insert

      New elements that will be added to the model when import is complete

    • Update

      Elements that will be updated after import

    • Referenced

      Elements that are referenced by other elements. If these are not resolved, either manually or automatically, a temporary replacement version of the element is created. These replacement elements are marked with a _notImported suffix.

  6. Note: If an element already exists in the destination model, importing it will overwrite the current element.
  7. Click OK.

    By default, the destination model with all imported model elements is validated using the Host Integrator Validator.

  8. Resolve any validation errors.

    If you are importing a model that contains an event handler, a reference to it is imported along with the parent element. However, you must manually copy the Java code from the model source Scripts sub-directory to the corresponding sub-directory in the destination model.

Visual Indicators

This icon... Indicates this...
Compound Procedure
Field (in recordset)
Column (in table)
Indicates that the model element has not changed. The element will be overlayed with the existing one.
The yellow asterisk indicates a new model element. This is an element that you might want to import.