NX How to change the angle value attribute mapped from NX which reflects radian value in TC.

How to change the angle value attribute mapped from NX which reflects radian value in TC.


Consider an attribute mapped the NX part attribute to TC ItemRevsion. The part attribute is angle value, but it shows radian value in TC. How to make an angle value show in TC?
 
Steps to duplicate >
1. Create an attribute(a3test) in ItemRevsion.
  - Attribute type : Double
 
2. Attribute Mapping NX to TC
 - { Dataset type="UGMASTER"
   "AR" : ItemRevision.a3test /master=cad /description="TestAttribute"
3. Create an expression in NX like below snap-

4. Create a NX template with an Attribute and add the expression value and Replace the attached "model-plain-1-mm-template.prt" which we just created with the attribute with NX Template in TC. Refer below snap

4. Launch NX from Teamcenter
 
5. Create a new item with a model mm template.
 
6. Tool > Expression
  - Change AP value to 180 degree
  - OK
 
7. Check updated ""TestAttribute" value in File > Properties
 
8. Save the part.
 
9. Check the attribute in TC ItemRevision.
 
10. The value is radian value(3.1415....) not degree(180 degrees).

Solution

1. Teamcenter has 'a3test' as a Double Property - it does not know anything about Units i.e. Degrees or Radians. It is just a Double value.
2. NX part template has a Native attribute which is 'double + type = Angle'. This definition comes from Native NX.
3. When you map the property 'a3test', NX does the "magic" of associating 'double + type = Angle' above with the 'a3test' in Teamcenter. Hence, a3test becomes a Double + type=Angle.
a. The second sentence in 3) is only valid in NX; TC still knows a3test as ONLY a Double Value
b. Experiment Part 1 - If you just map 'a3test' to NX attribute WITHOUT Native attribute [i.e. point 2) above], NX will know this as a Double value only.
4. Based on the above foundational understanding, if the user wants to assign a value in 'Degrees' let's say 180 degrees, NX will internally convert this value to SI units (i.e. in Radians) and assign it to Teamcenter.
a. Why? Because TC only knows Double value and any Double Value NX stores to Teamcenter has to be in SI units.
b. Experiment - Part 2 - From Part 1 of the Experiment above, if you assign 180 to this attribute, it will be saved as 180 only because NX does not need to convert to SI Units as there are NO units  

Notes and References

9803907

Hardware/Software Configuration

Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V1899
Function: ATTRIBUTES

Ref: 002-8513599