3D Templates Capture File-based Design Import

File-based Design Import (FBDI) enables content migration from V5 to 3DEXPERIENCE.

This page discusses:

V5 to 3DEXPERIENCE Data Import Table

The following table describes import correspondences between V5 file-based data and 3DEXPERIENCE content.

The statuses for import results are fully imported, partially imported, and not imported (-).

V5 Data Type 3DEXPERIENCE Content Type Import Result
Power copy Identical Fully imported
Note: Depends on the content of the powercopy (annotations, macros)
User feature Identical Imported
Knowledge pattern Identical Imported

Note: You must reference the ARM table instead of referencing the file based catalog
Document templateIdenticalPartially imported.
Notes:
  • Migrated. External documents specifications are lost.

  • After importing a document template, you must save the created engineering template. If you do not do so, the model is unusable.

Generative script--

Note: Replaced with the KML language.

Considerations

You should take the following considerations into account:

  • Document Templates import can only be done in asynchronous mode using the Use Mapping Tables option when importing the file.
  • External Documents are not properly supported. Links to external documents are lost and the user is warned.

  • The "Auto Inputs" do not exist any longer in PLM Templates and are replaced by simple Inputs.

  • Macro with arguments: instances cannot be modified.