An example of how preference TC_NX_Database_Attributes_For_Load works.
Solution
This preference controls the values of the attributes that are synched.
See the following key points to better explain this this setting:
1. User has a 3-level assembly (Assy1 -> Sub Assy1 -> Component1) which is being loaded in NX - the top level assembly (Assy1) will have all (i.e. customer defined and non-standard ) its mapped attributes (anything more than the system level attributes that are essential for the part viz. DB_PART_NO, DB_PART_NAME, etc.) synchronized on load.
2. If the user has NOT set this preference, then for the remaining 2 levels of the assembly (Sub Assy 1 and Component 1), only the essential attributes will be synchronized, i.e. the customer-defined and non-standard mapped attributes will not be synchronized on load. They will be synchronized on an as-needed basis, i.e. when the user wants to check the values of the other two levels of the assembly.
3. If the user has set this preference to = "*", all the attributes for all the levels of the assembly will always be loaded - whether the user wants it or not. That is what is deemed as "inefficient loading". Inefficiencies can creep in if the user has these attributes as columns in NX - by definition, this is telling the system to fetch these values on Load for all the levels of the assembly.
Notes and References
Hardware/Software Configuration
Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V12.0.2
Function: ATTRIBUTES
Ref: 001-9667105