When trying to create a relationship with another CI using GRLoader getting an error message "ERROR: Dependent CI not found"

Document ID : KB000010015
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

This document provides some possible causes of a "ERROR: Dependent CI not found" error when using Grloader to load relationships.

Instructions:

There are a few possible causes for this message:

1. One possible reason is that there may be multiple configuration items in the CMDB that have the same name. It's necessary to include other attributes in the load file to provide a unique value for the configuration item. For example, the load may be formatted as:

 

dependent_namedependent_serial_numbertypeprovider_name
service112345usesserver2
service167890usesserver3

Including "dependent_serial_number" helps to provide a difference between two configuration items that both have the name name.

 

2.  When embedded relationships are used in the spreadsheet, user should make sure that the CI has only "name" as the identifying attribute, if there are any other identifying attributes, the embedded relationships cannot be used.

 

For example:

This will fail:

 

nameclassserial_numberserves
System1Server1122335 
System2Server4445556 
Acd1ACD553431System1

 

But this will work:

 

nameclassserves
System1Server 
System2Server 
Acd1ACDSystem1

 

An "embedded relationship" differs from a non-embedded one in the formatting. In the samples above you will notice the embedded relationship actually specifies the relationship type in the header, "serves". In the example in point 1 you'll notice that the header is "type" and then the relationship type is specified below.

When using an embedded relationship you must only specify the name and class/family of the provider configuration item. Including other attributes will cause the error.