This documentation supports the 20.08 version of BMC CMDB, which is available only to BMC Helix subscribers (SaaS).

To view an earlier version, select the version from the Product version menu.

Namespaces and reconciliation

Almost all reconciliation definitions operate only on classes within a particular namespace. Even if an instance matches the qualifications that you specify, if its class is not in the specified namespace it cannot participate in reconciliation.

When you customize activities, you can specify multiple namespaces or even select an option that lets a definition operate in all namespaces. This gives you maximum flexibility when working in a CMDB that has several data model extensions installed, each using its own namespace. You can reconcile only CDM classes, only the classes from a particular extension, or any combination thereof.


Inheritance of reconciliation definitions by a subclass happens only within the namespaces specified for the definition. This can be important if you use BMC CMDB with other BMC products that extend the CDM.

For example, in a Precedence set, you might set an attribute precedence on the MarkAsDeleted attribute of BMC.CORE:BMC_BaseElement because it is the base class from which all others inherit so you can change the precedence value of MarkAsDeleted for all classes with one definition. If you define this attribute precedence for the BMC.CORE namespace, it does not apply to subclasses of BMC_BaseElement that were created by other BMC products with a different namespace, and Merge activities that use this precedence set will have unpredictable results.

Was this page helpful? Yes No Submitting... Thank you