Knowledge Basics Database Design Import

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
Parameters and Relations (formula, equivalent dimension, law, design table) inside a CATPart or CATDrawing	Identical	Fully imported
Relations (formula, equivalent dimension, law, design table) inside a CATProduct referencing user parameters at the Product level and parameters inside Parts	Idesign tabledentical	Partially imported (All the links are lost and all relations cannot therefore be used)
Parameters inside a CATProduct	Identical	Fully imported
External parameters: directly pointing another parameter whatever its location pointing a parameter through a publication pointing a parameter through an assembly contextual link.	Identical	Partially imported (The link is lost and the external parameter is isolated)
URLs added to objects i.e. geometric, body	Identical	Fully imported
VB Macros	Identical	Partially imported (not migrated: V5 VB APIs are not migrated into V6 APIs)
Catalog of Knowledge resources	Identical

Considerations

You should take the following considerations into account:

A CATpart Containing Knowledge Data in its Product: If a part CATIA file imported into V6 contains a relation at the product level that drives parameters located in the mechanical part, the model changes. In V6, there is no way to drive parameters upon relations that are not located in the same component. The relation must drive a parameter locally and the parts have to recover the output value using an external parameter. During the import, the correct V6 model is automatically generated.; When importing, a warning message appears meaning that some output parameters of the relation are located in some external components and that these particular components have been replaced with local ones.; The relation was in the product and is imported in V6, into the Knowledge Engineering Specification representation. This particular relation drives a local parameter (in the Knowledge Engineering Specification representation).; A formula and an external parameter have been created in the part to recover the output value of the formula and to drive the initial output parameter.
Isolate Relations: You can find information about the isolation of formulas, rules and checks links.; If at least one parameter of the Formula is located in the CATPart or CATProduct document that cannot be loaded or if parameters are missing, the formula is imported and the lost parameter is replaced by a cloned parameter and a warning appears.; For data anterior to V5R11 (V5R11 excluded), parameters are lost. For data posterior to V5R11 (V5R11 included), a clone parameter is created.; You can migrate data anterior to V5R11 using the CATAsmUpgradeBatch batch available from the Tools section.

Isolate Design Table Links

You can find information about the isolation of design tables links.

Classic Design Table: If a design table pointing to a .txt or . xls file cannot be loaded, it is not imported in V6. A warning appears to indicate which design table was not imported and which file prevents you from importing the design table. The parameters pointed by the design table keep their last values.

Embedded Design Table

If a design table pointing to a .txt or .xls file cannot be loaded but if it is embedded, it is imported in V6 without the link.

Others

Relations (Formulas, Equivalent Dimensions, Laws, Design Tables) inside a CATProduct referencing parameters in other CATProducts or parameters inside CATParts. If these parameters are output parameters of the relation, the link is no longer valid. The behavior is the same as in the case above and it creates a valid structure in V6 (see CATpart Containing Knowledge Data in its Product).
Relations (Formulas, Equivalent Dimensions, Laws, Design Tables) inside a CATProduct referencing component activities or product properties: These links are no longer valid.
Important: When a link to a parameter is no more valid in a V6 environment the parameter is replaced by local clones created during the DBDI process.
Knowledge Constraint Parameter Valuation: If the Knowledge relation is not located in the same document as the constraint which parameter is in input or output of the relation, the link is lost during the DBDI process. A deleted_Parameter will be created to replace the lost link on the relation.
These models can be repaired in V6 by editing or re-creating the relation to link the new parameter.
Valuation of constraint offsets from parametric relations: If you created a formula that valuates a constraint parameter in V5, in V6, a Knowledge Engineering Specification is created, the formula is imported into this Knowledge Engineering Specification, a local copy of the parameter (valuated by the formula) is created, an external parameter is created, and a formula is created in the constraint to retrieve the Knowledge Engineering Specification value.
If the constraint parameter is the input of a relation, the imported formula points to the constraint parameter.