Importing a Model Fragment

Model fragments can be imported from a file to restore an earlier version of the elements or to create a copy of a submodel while retaining the hierarchical structure.

Restoring or Copying Model Contents

You can import the model elements from a model fragment saved as a file in order to undo changes or to reuse the elements.

Note:

To copy and paste model elements within a model or in other models, use the corresponding commands on the clipboard.

Import always takes place in a system model with the same name as that from which the export took place. A new placeholder is created if no such system model can be found. You first need to determine whether the system model you want to use for the import can be identified by a name.

If the import should take place in the same Innovator model that the export took place in and you want to create a copy, you can rename the original system model or a deeper path component, e.g. the model or package.

If the import takes place in another Innovator model, renaming ensures that the path to be used as the target reached or that the import does not inadvertently take place in a path that already exists that you do not want.

Importing a Model Fragment to Restore an Earlier Version (Importing to Restore)

Prerequisites

Your role has the Versioning privilege.

You have already exported the submodel you want to restore as a model fragment in a file.

Import takes place in the system model with the same name as that from which the export took place. A new placeholder is created if no such system model can be found. You first need to determine whether the system model you want to use for the import can be identified by a name.

Context

A submodel that has previously been saved should be inserted to restore the state saved in the model fragment. The reference point is always a system model.

How to proceed

Select Model>Information>Import & Export>Import Model Fragment...

The Load Model Fragment dialog appears.
The Select... button opens a dialog where you can select the file you want. The file then appears with the complete path in the Model Fragment field.
To enable each element to be assigned on the basis of its UUID, even when it or its owner has been renamed, activate the Identify Elements By UUID radio button. This option is suitable for restoring an earlier version.
To use the UUID of the imported model element when replacing an element, activate the Adopt UUID On Import check box.
To set the behavior on conflicts, activate one of the radio buttons in the group of the same name.
Click on Import.
Check the results upon successful import. If you think that the copy was inserted in the right place then you only have a few touch ups to carry out.
A hazard icon might appear for some inserted path components. These are placeholders. Select all these nodes and change the Is placeholder element property in the Properties tool window to no. The placeholders are then replaced by the correct elements.
You should check the imported profiles in the Properties tool window for the system model and models (especially for placeholders) created upon import.

You have created a copy of the copied subtree which has the same structure.

Importing a Model Fragment while Retaining the Hierarchical Structure (Importing as Copy)

Prerequisites

Your role has the Versioning privilege.

You have already exported the submodel you want as a model fragment in a file.

Import takes place in a system model with the same name which the export took place from. A new placeholder is created if no such system model can be found. You first need to determine whether the system model you want to use for the import can be identified by a name.

If the import should take place in the same Innovator model that the export took place in, you can rename the original system model or a deeper path component, e.g. the model or package.

Context

A submodel which has been copied should be inserted into a new position once it has been given its hierarchical structure, i.e. into another system model or another Innovator model. The reference point is always a system model.

However, it is also possible to create a copy in the same system model by renaming deeper path components (model or package). Parts of the path that are not available are created as placeholders; this is how the path is designed.

How to proceed

Select Model>Information>Import & Export>Import Model Fragment...

The Load Model Fragment dialog appears.
The Select... button opens a dialog where you can select the file you want. The file then appears with the complete path in the Model Fragment field.
In order to be able to determine the paste locations from the model fragments in the file, activate the Identify Elements By Namespace radio button. This option is suitable for pasting as a copy.
To retain the existing UUID of an element when replacing it, deactivate the Adopt UUID On Import check box.

Otherwise, the UUID of the model element being imported is used. You then need to set the behavior on conflicts and activate one of the radio buttons in the group of the same name.
Click on Import.
Check the results upon successful import. If you think that the copy was inserted in the right place then you only have a few touch ups to carry out.
Change the name of the previously renamed path components to the names you want.
A hazard icon might appear for some inserted path components. These are placeholders. Select all these nodes and change the Is placeholder element property in the Properties tool window to no. The placeholders are then replaced by the correct elements.
Other elements shown as placeholders may have appeared if the import was carried out in another Innovator model. These can be e.g. classes needed as type. The selection set was incorrectly selected upon export in this case. You need to decide whether you also want to adopt these elements here or if you want to assign other types for the dependent elements. You need to make this decision individually for each case.
You should check the imported profiles in the Properties tool window for the system model and models (especially for placeholders) created upon import.

You have created a copy of the copied subtree which has the same structure.