I’m not sure I understand the failure.
As you say, you can create a relationship between CI’s in different datasets. When you try and reconcile the relationship to a target dataset it will expect both the source and destination CI’s to be in the target dataset as well. If you are expecting the relationship to be created in the target dataset with source and/or destination CI’s still in other datasets then I don’t think this is possible. To ensure that the relationship is merged ensure that the datasets of the source and destination CIs are merged first so that these CI’s are in the target dataset before the relationship is merged. By multi-stage recon job I assume you mean a job with multiple, sequential merge activities that process different datasets. This should prevent the error I think you are describing. Cheers Peter From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patchsk Sent: 04 September 2013 10:00 To: [email protected] Subject: Re: CIs in two different datasets, creating relationships and reconciling into Asset dataset ** We ran a few tests. Using the spoon or Asset UI we were able to create relationship instances between CIs belonging to different datasets.(So the client is not restricting it) However when trying to do reconciliation the identification is failing saying the Destination CI is not found in the source dataset. So seems like as others suggested the only way to push these to Asset dataset is either through multistage recon jobs and create relationships after merging CIs into a common dataset. On Friday, August 16, 2013 12:59:46 PM UTC-7, Peter Romain wrote: There is no problem creating relationships between CIs in different datasets. The relationship itself is, of course, in one dataset and a recon job for that dataset will process it. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected] <javascript:> ] On Behalf Of pritch Sent: 16 August 2013 20:11 To: [email protected] <javascript:> Subject: Re: CIs in two different datasets, creating relationships and reconciling into Asset dataset At least not out of the box. ----- Original Message ----- From: "Roger Justice" <[email protected] <javascript:> > To: [email protected] <javascript:> Sent: Friday, August 16, 2013 3:04:08 PM Subject: Re: CIs in two different datasets, creating relationships and reconciling into Asset dataset ** You cannot do relationships across Datasets, each one is unique. -----Original Message----- From: patchsk <[email protected] <javascript:> > To: arslist <[email protected] <javascript:> > Sent: Fri, Aug 16, 2013 2:25 pm Subject: Re: CIs in two different datasets, creating relationships and reconciling into Asset dataset ** This works if IPAddress is an attribute of ComputerSystem.(1-1) But if it is 1-Many then I need to create a relationship CIs between ComputerSystem and IPAddress. Note:I am using ComputerSystem, IP Address scenario as a hypothetical example. ComputerSystem is in DataSet A, and IP Address is in DataSet B. So as Tauf suggested we can copy the data from A and B into another staging dataset C and create relationships there and push them to production. But I am trying to see if we can avoid having another staging DataSet and if we can create relationships from different datasets directly and push them to ASSET. _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 <http://www.arslist.org> "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org> "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"
