GRLoader updates existing CI instead of creating a new CI
search cancel

GRLoader updates existing CI instead of creating a new CI


Article ID: 14530


Updated On:


SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager


The GRLoader updates an existing CI instead of creating a new one as expected.
The input files has a different name, class, family but the same dns name as an existing Ci. The existing CI has a serial number.
From the cora rules (the Serial Number is the most highly weighted field) I would expect that a new CI will be created. On the other hand cora says "CORA will recognize the same CI if DNS Name or MAC Address match and will create a new CI when they do not".

Why get the existing CI with a serial number updated, if the input file does not provide a serial number?


CA Service Desk Manager 12.9CA Service Desk Manager 14.1CA Service Desk Manager 17.0


CORA ignores the name of the CI if any other CORA property is provided. As a result CORA has ONLY the DNS Name, all the other passed in properties are null, to check if an existing asset exists or not. Since the DNS name is a match no new CI should be created.