On the ENOVIA side:
- In ENOVIA define an attribute called
Description
(string type).You can use a different
name.
- Add the
Description
attribute to the relevant ENOVIA types.
- Map the
Comment
attribute in the MCADInteg-CADToMxAttribMapping
attribute of the
Global Configuration Object to support attribute transfer from AutoCAD to ENOVIA. In
this case the mapping will be:
all,ISO A4:Comment|all,$$Description$$
- Map the
Description
attribute in the MCADInteg-MxToCADAttribMapping
attribute
of the current Global Configuration Object to support attribute transfer from ENOVIA to
AutoCAD. In this case the mapping will be:
all,$$description$$|all,ISO A4:Comment
Note:
The mappings for System attributes must always be in lowercase on the Mx side.
Refer to MQL commands for the ENOVIA-to-CAD attribute mapping and CAD-to-ENOVIA attribute mapping.
To list the available GCOs with their Bus ID and revision, run the following command
MQL>temp query bus *Global* * * select id;
To modify a GCO attribute from a GCO, run the following command
MQL>modify bus <busname> <attributename> "<attribute value>";
For example, to modify GCO attributes for Connector for AutoCAD GCO with Bus ID 12345,
MQL>modify bus 12345 MCADInteg-RenameFilesInServer True
;
From the mapping, the integration knows which block is read for attributes. This allows the user to
synchronize the block attributes automatically, without the involvement of user interaction.
If the drawing has multiple instances of the same block, the user is prompted to select one of
the instances of the block.
Note:
The Attributes area of ENOVIA New dialog box displays the
attributes mapped in the IEF-CADToMxAttribMapping
with the values stored in ENOVIA, and not on the CAD file.