Hi, I'm quite sure we had the same issue, and regards to BMC this is as designed. However, defect SW00364806 was created. But this is now in this state: "Not A Defect with Target Release Version = Future Patch Release."
Got some information that this is fixed in 7.6.3 relase, but not tested. -- J 2010/11/8 Sergio Tomillero <stomill...@gmail.com>: > Hi folks, > This is the situation: > I have 2 source datasets and I want get info from them to a destination one. > From source dataset 1 I want to get the name > From source dataset 2 I want to get the description > Records are matched by AssetId. AssetID is the same for a record that exists > in source dataset 1 and sourcedataset 2 > For example: > Dataset 1: > Asset ID: ID888 > Name: FUN 888 jkr1 > Description: FUN 888 from model 11 > > Dataset 2: > Asset ID: ID888 > Name: FUN 888 jkr33 > Description: FUN 888 model 22 > > What I want to reach is: > Dataset 3 (destination dataset): > Asset ID: ID888 > Name: FUN 888 jkr1 > Description: FUN 888 model 22 > > I have created a job with the next: > > - Identification activity: > o Dataset configuration: > - Dataset 1 > o Additional parameters: > - Production dataset: Dataset 2 > - Generate Id: checked > > With this I do that RE identifies the CI and assigns the same > Reconciliation Identity to the record ID888 in both datasets (dataset 1 and > dataset 2) > > - Merge activity 1: > o Source dataset: Dataset 1 > o Destination dataset: Dataset 3 > o Calification : I limit by the class of the CI > o Precedence: > Association precedence SET = Group 1: > • Dataset = Dataset A > Preference set = Group A > > Decisive Value: 400 > o Group A: > Rule: > • Atributte: Name with 750 of preference dataset value > • Dataset =Dataset 3 > > Preference set =Group 3 > > Decisive Value: 500 > o Group 3: > Rule: > • Class: CIClass with 600 of preference dataset value > - Merge activity 2: > o Source dataset: Dataset 2 > o Destination dataset: Dataset 3 > o Qualification : I limit by the class of the CI > o Precedence: > Association precedence SET =Group 2: > • Dataset = Dataset B > Preference set = Group B > > Decisive > Value= 400 > o Group B > Rule: > • Atributte: Description with 750 of preference dataset > value > • Dataset =Dataset 3 > Preference set = Group 3 > > Decisive > Value = 500 > o Group 3: > Rule: > • Class: CIClass with 600 of preference dataset value > > > When I run the job: > 1. Merge activity 1 creates a record in dataset 3 > 2. Merge activity 2 updates the record in dataset 3 that previously merge > activity 1 generated, and only dataset 2 information is in dataset 3: > > Asset ID: ID888 > Name: FUN 888 jkr33 > Description: FUN 888 model 22 > > And generated log file is void. > > Any idea about what I am not configuring correctly? > > ARS version: 7.5 p5 > Reconciliation Engine: 7.6 > > Thank s a lot > Sergio Tomillero > > -- > View this message in context: > http://ars-action-request-system.1093659.n2.nabble.com/Reconciliation-Engine-Cannot-merge-data-from-two-datasets-to-a-destionation-one-tp5718360p5718360.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"
