Hi Expert,
There are no relationship between those CIs.
Please could you explain in detail for an ID rule.?
Cheers,
Abhi.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are,
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.
Hi Chetan,
The steps provided by you in last update is not working so please suggest on it.
Early response will be highly appreciated.
Cheers,
Abhi.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where
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
Can you attached the normalization job logs?
Regards,
Chetan Shinde
On Thu, Dec 3, 2015 at 8:00 AM, Abhishek Anand
wrote:
> Hi Chetan,
>
> The steps provided by you in last update is not working so please suggest
> on it.
>
> Early response will be highly appreciated.
>
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
6 matches
Mail list logo