If you include multiple source datasets in 1 job with the same precedence value, you'll get the data from the source that was merged last. You would need to update your precedence values or run 2 separate jobs to control which dataset is merged second. And fix C. Jason Bess
________________________________ From: Scott Philben <[email protected]> To: [email protected] Sent: Monday, October 7, 2013 10:25 AM Subject: Re: CMDB Precedence Setup Question ** Correct. I missed that in the diagram. C = 600 so neither of them will update it, it appears. On Oct 07, 2013, at 10:20 AM, Roger Justice <[email protected]> wrote: ** >It is not A against B, it is A against C and then B against C. What is the >value for the attribute for C. >-----Original Message----- >From: Scott Philben <[email protected]> >To: arslist <[email protected]> >Sent: Mon, Oct 7, 2013 9:04 am >Subject: CMDB Precedence Setup Question > > >** >Listers: > > >If I have two datasets (A, B) reconciling into a third (C) and I set >precedence rules such that A = 500 and B= 500 for a particular attribute >(other attributes are set up with different precedence rules), which dataset >wins when it comes time to copy into C for that particular attribute? > > >Thanks. > > > >_ARSlist: "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"
