Understanding default precedence

The position of a default determines its precedence. You set defaults on a particular item, but Teamcenter applies them globally to the whole currently loaded structure. Derived defaults always take precedence over fixed defaults. If you move a default up or down the structure, conflicts may occur. If you have set conflicting fixed default values for the same option in a structure, Teamcenter always uses the first default value it finds, according to the following rules: A default that is higher up the tree in a direct path takes precedence. Defaults at the top level always take precedence. If you set conflicting derived default values for the same option in a structure, Teamcenter displays an error message when you attempt to save the option default or set the option value in the variant rule that causes the conflicting derived default to apply. The error may also appear when you expand the structure to the point that the conflicting derived default is loaded.