The asset merge feature prevents duplicate assets from appearing in your database. During the data upload, based on the keys that you select, assets with duplicate keys are merged to form one asset in the system.
When assets are merged into one, their data is summed up. For example, you create a cell-phone resource and specify manufacturer, model, and barcode 10001. If you create another cell-phone asset with status, comments, and barcode 10001, then these two assets are merged based on the barcode. The resulting asset has manufacturer, model, barcode, status, and comments pulled into one asset. If the data classes on both assets which were merged contain data, then the data from the last uploaded asset is written to the Configuration Management Database (CMDB). For example, consider an asset had manufacturer ABC. If another asset with the same barcode is uploaded with manufacturer XYZ, then the merged assets show the manufacturer as XYZ.
You can merge multiple keys, but you must ensure that all keys match. For example, you check Barcode and Serial Number and then you upload the resource from a barcode device. The key only merges with an existing resource if both the barcode and the serial number match.
This task is a step in the process for setting up the Barcode Solution environment.