Attribute resolution

A name can identify multiple property types especially if the configuration contains models with many different profiles. To prevent ambiguity the user may qualify a profile attribute or profile relationship with a profile name. Custom attributes, custom relationships, UDPs and system attributes also share the same name space. MM uses the following precedence rules in resolving ambiguity among the custom attributes, custom relationships, UDPs, system attributes and any unqualified profile attributes or profile relationships. The rules are listed in descending order:

1. System attributes and Source History attributes
2. Custom attributes
3. Custom relationships
4. Data Profiling attributes
5. Profile attributes
6. Profile relationships
7. UDPs