V4 Integration Database Design Import

Database Design Import (DBDI) enables the migration of CATIA V4 data stored in a legacy database into 3DEXPERIENCE.

This topic specifies the import correspondences between V4 data types and 3DEXPERIENCE content types, and the import result. The statuses for import results are fully imported, partially imported, and not imported (-).

This page discusses:

Common Import Behavior

This section describes the behavior of CATIA V4 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.

V4 Data Type 3DEXPERIENCE Content Type Import Result
Model Representation Imported as representation.

It contains the same information as the models. No modification of data during import (except the name of the model). The model used as a representation in the CATIA V5 Product Structure is imported as an instantiated Representation.

Session - Not imported.
Library - Not imported.
MML Links -

The link will be isolated.

It is recommended to import first the pointed documents, and then the pointing documents within the same session

ENOVIA VPM V5 Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

ENOVIAvpm Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

X-CAD Design Management Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

SmarTeam Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

Adapter for X-PDM Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.