If you have relationships between those CIs, they will identify first and
that may result in "unexpected" results.
Also keep in mind that if you have an ID rule and that ID rule doesn't meet
all the criteria in the rule, it's not going to find a match. So if your
rule has Tag and SN, and only SN matches, ID moves to the next rule...
Janie
On Thu, Dec 3, 2015 at 5:06 AM, Danny Kellett <
dkell...@javasystemsolutions.com> wrote:
> Hi Abhi
>
> The best thing to do is create one record to play with and enable the
> recon + API + sql log and see why the identification job didn't find it in
> the dest source
> Regards
> Danny
>
> > On 3 Dec 2015, at 12:58, Abhishek Anand wrote:
> >
> > Hi Experts,
> >
> >
> >
> > This is a data load import for where we are importing delta’s
> (changes to existing CIs). The data was imported fine but when
> Reconciliation ran, instead of updating the existing record, it has created
> new ones even though key information such as serial number were the same.
> >
> > We can see no reason why these weren’t update over the existing CIs.
> >
> >
> >
> > Early response ill be highly appreciated.
> >
> >
> >
> > Cheers,
> >
> > Abhi.
> >
> >
> ___
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> > "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"
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
