When you set up the reconciliation jobs you can adjust the weight of the attributes that exist so that, for example, one dataset provides the name and the other provides the IP address. The key is to set up each dataset so that the attribute that makes them common exists in both datasets. Otherwise reconciliation will just create 2 CIs, and that is not what you want at all. ☺
Run the first recon job using DataSet A which creates the CI, then run the second recon job using DataSet B which merges the data in BMC.ASSET with the data from Dataset A. .: Mike T :. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patchsk Sent: Friday, August 16, 2013 12:22 PM To: [email protected] Subject: CIs in two different datasets, creating relationships and reconciling into Asset dataset ** I have data coming from two different data sources for different CI Types. (Ex: Computersystems in DataSet A, IPAddresses in DataSetB). So I need to create relationships between them and eventually reconcile them into production dataset. No issues with CIs because they can be in different datasets and we can have different reconciliation jobs to push them to production dataset. How to handle relationships in this case. Is it allowed to a) Create relationships between CIs in different datasets. b) Does reconciliation engine/jobs support reconciling relationships of CIs belonging to different datasets? _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"
