If you use asset sandbox then, when you create a new CI from an existing CI,
the relationship includes the 'old' CI in the production dataset and the
'new' CI that is created in the sandbox dataset.

 

The recon job merges this to production so it looks like it should be able
to cope with Scott's scenario.

 

Scott, if the CI's in the two datasets will never be duplicated why not make
life easier and just import them all into one dataset?

 

What is the relationship job that ran to create the relationships?

 

 

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Roger Justice
Sent: 02 March 2011 22:44
To: [email protected]
Subject: Re: Trying not to Merge a whole dataset?

 

** Your logic will not work since items in A should not be related to items
in B. Each Data Set is independent and the merge is to move the data and
relationships of one dataset into BMC.Asset. Then you do an ID job against
BMC.Asset with the second dataset to get the same CI to get the right
ReconID so that when you merge the second data set both the CI and
relationships are merged.

 

-----Original Message-----
From: Scott Philben <[email protected]>
To: arslist <[email protected]>
Sent: Wed, Mar 2, 2011 4:44 pm
Subject: Re: Trying not to Merge a whole dataset?

** 

I ran an ID job on B based against itself (this is the first import, no data
in BMC.ASSET yet). I got ReconIDs auto generated for all my B CIs. Now I
want to relate and merge only those that relate.

 

Still can't figure it out.

 

 

 

 

On Mar 2, 2011, at 1:35 PM, Roger Justice wrote:





** How did you do the Identification between B and BMC.Asset?

 

-----Original Message-----
From: sphilben <[email protected]>
To: arslist <[email protected]>
Sent: Wed, Mar 2, 2011 1:20 pm
Subject: Trying not to Merge a whole dataset?

** 

All:

 

I have two datasets (A and B). I want to merge all of dataset A to BMC.ASSET
but only those in dataset B that are related to CIs in A. So after my ID job
I ran a relationship job that created HOSTEDSYSTEMCOMPONENT entries and
filled in the SystemName field on B. Can I use that field now to restrict
the merge on B?

 

I tried setting up a merge job on B with one activity: merge source B to
BMC.ASSET using the Default Merge Set. I then added a qualification on the
class with 'SystemName' !=  $\NULL$ in the Qualification* field. 

 

When I run the job nothing happens. No records get copied to BMC.ASSET.

 

Can I even do something like I am trying to do? Can I restrict a dataset
merge in this way? Or do I have to merge everything?

 

Thanks.

_attend WWRUG11 www.wwrug.com <http://www.wwrug.com/>  ARSlist: "Where the
Answers Are&qu 

_attend WWRUG11 www.wwrug.com <http://www.wwrug.com/>  ARSlist: "Where the
Answers Are"_

 

_attend WWRUG11 www.wwrug.com <http://www.wwrug.com/>  ARSlist: "Where the
Answers Are"_ 

_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"

Reply via email to