Common Import Behavior
This section describes the behavior of CATIA V5 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.
| 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 template | Identical | Partially imported. Note:
Migrated. External documents specifications are lost.
|
| 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.