NX Callout attribute is not the same as Find No

The assembly component CALLOUT attribute value does not match the Find No value in Teamcenter.


The Customer Default, "Callout Attribute Title", is set to DB_SEQUENCE_NO, why won't the CALLOUT component attribute in NX synchronize to this value from Teamcenter? 

Solution

The Callout column in the Assembly Navigator will report the CALLOUT value at the 'Component' level. 
Go to Component Properties and look at the Callout attribute. The 'Instance' level of the Callout attribute is correct and matches the Teamcenter Find No. The Instance level of the attribute is what is read from 
(and will write to) Teamcenter; however, the Component level of the CALLOUT attribute is different. Out of the box, the Callout attribute value can be overridden at the Component level to be different from the Instance level.


To turn this off so the Component level value of the CALLOUT attribute is always the same as the Instance level, set this Customer Default: 
1. Assemblies-->General-->Instance Attributes (tab)'. 
2. Toggle OFF 'Allow CALLOUT Attribute Override'. 
3. OK the Customer Defaults dialog. 
4. Re-start NX. 
Now when the assembly is opened and reviewing the Attribute Properties on one of the components, notice at the "Component Level", the CALLOUT attribute is locked and cannot be modified. However at the Instance level, it is still modifiable. 


Now when the assembly is opened, the component level Callout will always be the same as the Instance level Callout and match Teamcenter.

Notes and References

Hardware/Software Configuration

Platform: all
OS: n/a
OS Version: n/a
Product: NX
Application: NXMANAGER
Version: V11.0.2
Function: ATTRIBUTES

Ref: 001-9062212