On the destination dataset you can set the precedence weight to 1000 (max value). In our environment we have 4 different data sources that reconcile to our CMDB. On the destination I set those attributes that need to be permanent at 700 with the data set precedence set at a lower value than the attributes. Keep in mind the value is arbitrary as long as the destination dataset has a higher value than the source datasets. It works like this:
BMC Asset: 500 precedence weight on dataset, 700 on attributes that are permanent Discovery: 400 precedence weight on dataset, 600 on attributes that I want propagated What this allows is a default behavior of not propagating any attributes except for those that you specifically want propagated. You will need to coordinate those attributes among the discovery datasets to ensure you don't have more than one that is trying to update the same attribute. Also keep in mind that the Dataset Merge Precedence Sets will also function as a tie breaker by order, with the first (lowest number) in the set winning in case of a tie. Hopefully this helps. Jim -----Original Message----- From: Sergio Tomillero [mailto:stomill...@gmail.com] Sent: Wednesday, March 09, 2011 4:51 AM Subject: Recon Engine. How to give the maximum precedence to destination's dataset specifics attributes? Hi all, I have information in two source datasets. Applying certain weights, I reconcilie each one, by separate, to the same destination dataset. The result is that in destination dataset, for the same ci, I have information from source one and source two according to my convenience. This is ok. Anyway, there are some fields in destination dataset that I do no want to be updated from sources, except if they are null in destination. For instance, working in the destination dataset if I updated the value of the field 'Description', I would want to keep this value, not replaced from source dataset, when a reconciliation from sources took place, except if Description were null in the destination dataset. How to achieve this behavior? The problem is that I cannot include destination dataset in the Merge Precedence because it causes an error if a job from a source dataset is launched twice. I use CMDB 7.6.0 p1. Thank you in advance, Sergio Tomillero -- View this message in context: http://ars-action-request-system.1093659.n2.nabble.com/Recon-Engine-How- to-give-the-maximum-precedence-to-destination-s-dataset-specifics-attrib utes-tp6153343p6153343.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
