Importing or Exporting Model Fragments
Model fragments are created by exporting an active model's contents and/or its configuration. In doing so, you store a submodel as a file so that you can undo changes or reuse the submodel at another position in a model.
Model fragments are created by exporting an active model's contents and/or its configuration.
Model fragments thus represent a submodel, which you save as a proprietary XML file. Exporting and importing these model fragments gives you the option of exchanging groups of model elements using the file system and using them for subsequent use cases:
-
Undo changes or deletes (restore)
Export relevant model areas before making a big change or at regular intervals. This means you can always import this model fragment if you need to restore an earlier state.
-
Copy subsystems (duplicate)
Model fragments stored in a file are an excellent way of reusing subsystems at other positions in a model while retaining their structure.
For most model and profile elements in an Innovator model, a Universally Unique Identifier (UUID) is assigned at creation. The UUID enables a model element to be identified within various version states of an Innovator model. This enables elements which were renamed or moved to another namespace in a later version to be identified in spite of modifications to structural properties.
Note
Roles used for logging-in require the Use Model Fragments privilege.
This chapter contains the topics: