If system (in case of ENOVIA) or summary (in case of Inventor) attributes are used, they need to be enveloped by "$$" for correct identification.
For example,
$$Title$$, $$Author$$
Following table explains the supported system attributes in ENOVIA for to & from transfer:
Direction
|
Description
|
Owner
|
Type
|
Name
|
Revision
|
To ENOVIA
|
Supported
|
Supported
|
Not supported
|
Not supported
|
Not supported
|
From ENOVIA
|
Supported
|
Supported
|
Supported
|
Supported
|
Supported
|
Use the following steps to add a Summary attribute, for example, Comments
in Inventor and mapping it to Description
in ENOVIA.
Inventor side:
-
Open a part in Inventor and click File > Properties > Summary.
-
Assign the value say "Design Part" in the text box provided against the attribute "Comments".
3DEXPERIENCE side:
-
Define in 3DEXPERIENCE, an attribute called "Description" (string type). (Note: Name can be different)
-
Add this attribute to the relevant 3DEXPERIENCE types. In this case say "INV Component" and "INV Versioned Component".
-
For supporting Inventor to 3DEXPERIENCE attribute transfer, map the Description attribute in "
MCADInteg-CADToMxAttribMapping
" attribute of Global Config Object. In this case the mapping will be:
component,$$Comments$$|INV Component,$$description$$
-
For supporting 3DEXPERIENCE to Inventor attribute transfer, map the Description attribute in "
MCADInteg-MxToCADAttribMapping
" attribute of current Global Config Object. In this case the mapping will be:
INV Component,$$description$$|component,$$Comments$$
You need not add mappings for Versioned types. Mappings are necessary only for major types. X-CAD Design Management internally handles same attributes for Versioned types.