About Attribute Mapping

Attribute mapping helps you synchronize CATIA V5 attributes with the exposed database attributes.

This page discusses:

When you perform a save in CATIA V5, you can transfer the attribute values from the CATIA V5 file to 3DEXPERIENCE. When you perform Open in CATIA V5, you can transfer the attribute values from 3DEXPERIENCE to CATIA V5.

Attribute mapping can be defined in two ways:

Important: When a CAD attribute is mapped from 3DEXPERIENCE to CATIA V5, the attribute value is updated in CATIA V5 only if the object is modified outside CATIA V5.

Supported Types

For attribute mapping, CATIA V5 types and 3DEXPERIENCE native types are supported.

Supported Attributes

  • You can map any V5 attribute type to 3DEXPERIENCE string attribute type (i.e. Real->String, Boolean ->String)
  • You can map any V5 attribute type to its corresponding 3DEXPERIENCE attribute type (Real<->Real, Boolean<->Boolean, Integer<->Integer, String<->String)
  • Mapping is supported when its value matches the target attribute type and unit, i.e.
    • String->Integer
      • If V5 String attribute value is “3”, mapping will be successful and 3DEXPERIENCE integer attribute value will be 3
      • If V5 String attribute value is “3.2”, mapping will not be successful as 3DEXPERIENCE integer attribute value cannot be 3.2
    • Real->Integer
      • If V5 Real attribute value is 3, mapping will be successful and 3DEXPERIENCE integer attribute value will be 3
      • If V5 Real attribute value is 3.2, mapping will not be successful as 3DEXPERIENCE integer attribute value cannot be 3.2
  • While mapping attributes, you can have different locales between the client and the server (for example the client is French and the server is English).
    • Real <->Real attribute mapping is defined
    • When you save 3,6 V5 attribute, the value will be 3.6 in 3DEXPERIENCE

Notes:
  • Multi-valuated attributes are not supported for attribute mapping.
  • Date attribute type mapping is not supported.

Supported Keywords

Given below are the prefixes and the CATIA attribute types:

1. CATIA system attributes sys:

OOTB attributes: PartNumber, Description, Revision.

2. CATIA user-defined custom attribute cus:

User-defined custom attribute (Edit > Properties > Define other properties > New Parameter of type)

The cus: attributes are only supported for parts, EC's and products.

The behavior of the create: keyword is not applicable for CATIA V5 to 3DEXPERIENCE platform mapping; it is not supported. This keyword is not supported for instance attribute mapping.

3. CATIA user-defined parameter param:

The param: attributes are supported in parts, products, EC's, drawings and shapes.

Tools > Formulas > New Parameter of type.

By default:.

  • The part number of products and parts on CATIA V5 files is mapped to V_Name ("Title”) attribute of the VPMReference database object and vice versa.
  • The description of products and parts on CATIA V5 files is mapped to V_description ("Description") attribute of the VPMReference database object and vice versa.

Parameter Attribute Mapping

You can map parameters under geometrical sets, parameter set, or parameter subset - the ones under main structure and different features to 3DEXPERIENCE. You can view the parameters in the Formulas window.

Main structure: product, part, embedded component, drawing.

Features: PartBody, geometrical set or external parameters of a part.

To map a parameter, you must use the string visible in the Formulas window (name or name with path) of CATIA V5.

If you change the CATIA V5 language, the parameter's name, or name with path will be translated if those parameters or set/subsets are not renamed. For example, COQ\Circle.2\Radius seen in CATIA V5 formula window launched with English is changed to COQ\Cercle.2\Rayon when the language changed to French. It is recommended to rename parameters so that they are not affected by CATIA V5 language change, and the mapping works for all CATIA V5 environments.

Note: The parameters on instances are not supported for attribute mapping.