About merging duplicate configuration items

Article:HOWTO64067  |  Created: 2011-12-20  |  Updated: 2011-12-20  |  Article URL http://www.symantec.com/docs/HOWTO64067
Article Type
How To


About merging duplicate configuration items

The feature of merging configuration items lets you merge duplicate configuration items.

You can merge the configuration items only of the same configuration item type. For example, you can merge the two assets: a printer and a network printer. You can merge two contracts. But you cannot merge an asset and a contract.

When you merge two configuration items, you select the configuration item that you want to keep. For the data classes that both configuration items have, you select the data class that you want to keep. If a data class exists only for the configuration item that you decide to delete, the data for this data class is also deleted.

Associations of the configuration item that you decide to delete are transferred to the configuration item that you keep. If there is more than one association of the same type, only the newest association remains.

You can use tasks and rules to automate recurring configuration item merges.

The base for merge tasks and rules are the merge keys. Predefined configuration item type data classes define the merge keys. For example, to create a merge rule for desk phones, you select the Desk Phone configuration item type. You can then select one of the available merge keys. The list of the merge keys is based on the default data classes for Desk Phone configuration item type, such as a phone number.

You can use Connector Solution to define the additional resource lookup keys that appear in the Merge Key drop-down list.

A custom data class that you add to a predefined configuration item type cannot be used as a merge key.

See Merging two configuration items.

Legacy ID


Article URL http://www.symantec.com/docs/HOWTO64067

Terms of use for this information are found in Legal Notices