You're correct, that is exactly how I'm doing it. Except for one thing which 
doesn't have to do with the error message: for step 5, I click on  Select 
Source and find the CI I want to relate, then for Destination I use the CI that 
I was previously looking at (which at the beginning of this step was in the 
Source).

Thank you for clarifying the reconciliation error message issue.

Marcelo

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
Sent: Friday, December 11, 2009 1:37 PM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component

**
OK.  So is this what you're doing?


1.       Search for CI from CMDB Console via Browse Instances

2.       Click the View button to view the CI you want to add a relationship to

3.       Click View Relationships on the CI record

4.       Choose a Namespace and Relationship Class and then click Create

5.       On the Relationship record, click the Select Destination button

6.       Find another CI and then click OK

If I do that, it seems to copy the destination's Recon ID into the Recon ID 
field for the relationship.  That would account for the error that you're 
getting, since reconciliation IDs need to all be unique (unless they're zero).  
I'm not sure why it wants to be copying the destination's recon ID into the 
relationship's recon ID.  If it really wants to have one, it should simply be 
generating a new one.  It's possible this is a bug in the workflow; you might 
consider taking it up with BMC.

Otherwise, if you're doing everything in BMC.ASSET like this, there probably 
isn't really a need to have Reconciliation IDs on everything, since you're not 
trying to reconcile anything in, and even if you were, you usually 
auto-identify BMC.ASSET anyway which will add a recon ID wherever one is 
missing.  So, I'm thinking that you probably can simply replace the recon ID 
that it's copying into the Recon ID field of the relationship with a zero (0).  
I tried that and didn't get an error.

Perhaps others have other thoughts on this?

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Martinez, Marcelo A
Sent: Friday, December 11, 2009 12:11 PM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component

**
Yes sir.. 2.1.00 Patch001

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
Sent: Friday, December 11, 2009 12:59 PM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component

**
Did you already say which version of the CMDB you're working with?  I've been 
guessing 2.1, but wanted to make sure...

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Martinez, Marcelo A
Sent: Friday, December 11, 2009 11:50 AM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component

**
answer :) .. maybe you can shed some (more) light here...
I am manually relating them via the CMDB console. The ReconciliationIdentity is 
automagically being generated, but it always generates the same one (based on 
the CIs I select, I think).
I am not using the SANDBOX, I'm doing them straight into BMC.ASSET.
Am I doing something wrong?

Marcelo

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
Sent: Friday, December 11, 2009 11:51 AM
To: [email protected]
Subject: Re: CMDB mapping question: dependency vs. component

**
Silly question, but are you manually setting the recon ID?  Or do you have the 
Sandbox turned on?  Or are you manually creating these relationships in the 
CMDB forms as opposed to relating them in the AST forms?  Basically, how are 
you going about creating these relationships?

Lyle
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_


NOTICE: This email message is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message.

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to