Details
---------------
How to make attribute mapping work as stated in TDocs?
From Whats New in Teamcenter 11.2
Support for mapping a single CAD attribute to multiple Teamcenter properties.
For example, you can map a part name to both of the corresponding item and item
revision names, ensuring both names are changed if the part name is changed.
One-to-many mappings are defined in a mapping file that is imported to the
Teamcenter server. An example of the necessary mapping is as follows:
DB_PART_NAME : Item.object_name /master=cad /description="Part Name"
DB_PART_NAME : ItemRevision.object_name /master=cad /description="Part Revision
Name"
Note
One-to-many attribute mappings must be mastered in the CAD system, that is, you
must specify /master=cad or /master=both in the mapping file. Alternatively,
if you do not specify a master, Teamcenter uses /master=both . If you specify,
/master=iman or /master=none , the import fails.
Conversion of hard-coded CAD attribute mappings (DB_PART_NAME and
DB_PART_DESC ) to user-defined mappings that can be modified to meet business
needs.
Solution
To support this functionality please set the following TC preference
TC_NX_allow_attrsync_master_with_item=yes to get the attributes sync in
multiple locations.
If this is undefined or set to "no" then it is not possible to write to
properties on the Item Master Form from NX.
Notes and References
TDOCs/IR7641637
Hardware/Software Configuration
Platform: INTEL
OS: windows
OS Version: 764sp1
Product: NX
Application: NXMANAGER
Version: V10.0
Function: ATTRIBUTES
Ref: 002-7007801