XML Troubleshooting Tips
NullPointerException errors
In general, tags requiring a fully qualified Java class name should not be added to a custom xml and left empty. This may cause NullPointerException errors.
Changing Load Rule index values
Changing the Load Rule index values doesn't just affect the Load dialog, it affects an assembly's children in any structure browser where you can expand that assembly. For example, if you change the Highest Revisions index to 1, the Load dialog defaults to loading the highest revision children for an assembly. However, expanding the assembly in a structure browser also displays the highest revision children in that assembly.
If you want to have the highest revision children in the Load dialog, and the "As Stored" children in all other browsers, you must keep the default index settings.
Assigning custom display names
It is possible to assign different display names for the DESCRIPTION attribute according to the class in which the attribute occurs. This appears to display correctly in some screens (such as Search), because you can only see attributes of one class. If, however, you are in the Recent List tab, all DESCRIPTION attributes from different classes are displayed in one column. The name of the column will be the <DisplayName> of the last DESCRIPTION attribute in your custom xml file.
Since the DB attribute is the same in each class, a Java customization may be required. The best results may be achieved by editing the schema and either changing the attribute name from DESCRIPTION to something else, or adding a new attribute with the desired name.
Redefining an existing class
Be careful when redefining an existing class in your custom xml file. Removing attributes may cause changes in the information displayed. For example, the BOM Editor will not display the Show in report checkboxes if you remove the BOM_FLAG attribute from DMMasterdata or DTMasterdatabase (depending on the schema used), or the Manually Managed Item checkboxes if you remove the BOM_DESCRIPTION2 attribute from DMMasterdata or DTMasterdatabase.
Customizing the BOMTable list
If you define BOM tables in your custom xml file, they replace the existing definitions. They are not merged with the existing BOM tables defined in wmconf.xml. You must copy any desired <BOMTable> tags from wmconf.xml into your custom xml file.
TableColumnModel performance considerations
If you enable the File to Load column on any UI other than Load, it will affect performance. It should only be included in the Load TableColumnModel.