Merge uses the Recon ID to either merge or not merge an entry. If a new entry is added the automatic identification will give it a Recon ID, if the ehtry exists and the qualification works it get the recon ID of the existing CI.
-----Original Message----- From: hornetload1 <hornetlo...@gmail.com> To: arslist <arslist@ARSLIST.ORG> Sent: Wed, Dec 12, 2012 7:42 am Subject: Re: NOT merging a new record into BMC.Asset **Hi Roger, Thanks for the input. Do I need to setup a Manual Identification? How does this only merge a record if one exists? Thank you. On Mon, Dec 10, 2012 at 11:49 AM, Roger J <rjust2...@aol.com> wrote: ** Do not allow Auto Identification on the dataset to be merged. ---- Original Message ---- From: Joe <hornetlo...@gmail.com> To: arslist <arslist@ARSLIST.ORG> Sent: Mon, Dec 10, 2012 12:47 pm Subject: NOT merging a new record into BMC.Asset Hi all, Our scenario: Bringing in an external spreadsheet of 5 fields. Once brought into the staged dataset via AIE the records are normalized and reconciled into the BMC.Asset Dataset. We are utilizing Name to identify on in ComputerSystem. Issue: Because this spreadsheet is completely human entered and not an export from any system there is a chance of human error. We would like to ensure that if a Name is incorrectly input into the spreadsheet it is not reconciled into the CMDB. Question: How to I exclude a record from reconciliation into BMC.ASSET if it DOES NOT currently exist (from the staged dataset). Thank you, have a great day. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
