The CreatorCon Call for Content is officially open! Get started here.

CMDB dependency view

Vijay Kumar4
Mega Guru

In my org, there are around 1,517 configuration items that were added manually. Currently, no map has been created for these items, so nothing appears in the dependency view. Is it possible to manually create relationships/dependencies for these 1,517 items? Also, would this require specific knowledge about the assets within the configuration items?

VijayKumar4_0-1758562269087.png

 



#cmdb #configurationsItem #servicenow

1 ACCEPTED SOLUTION

@Vijay Kumar4,
To create the relationship you need to create them in cmdb_rel_ci table. See example snip below.

VikMach_0-1758642484190.png

 

As you are doing it manually, yes you will have to do it for all CI's because there are different classes. (I don't know how many classes you have at the moment.) 
But you can achieve it quicker if you do it in the Excel sheet first and then upload it through transform map. Don't worry even if it goes wrong for any CI, you can correct the relationship anytime you think is not looking right as per your infra. There is a check box that shows your Suggested relationship which I highlighted earlier in my first reply.  

 

 

VikMach_2-1758643227577.png

 

VikMach_1-1758642988193.png



Regards,
Vikas K 

View solution in original post

3 REPLIES 3

VikMach
Mega Sage

@Vijay Kumar4,
Yes, you can create relationship manually. To create it manually you can take help of "Suggested Relationships" in the CI Class Manager. For example, if you are creating relationship for Server class and you are not aware of all the related resources, you can look at the relationship mapping from the suggestions. See snip below.

VikMach_0-1758563562044.png


When you want to understand what "type" of relationship to create you can click on the class and it will show you the relationship that is suggested. See snip below.

 

VikMach_2-1758564065323.png

It is also documented in the ServiceNow Docs. Take a look from there as well if you get stuck.
https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/administer/form-administratio...

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

 

If you are doing some CSDM related classes as well then follow the relationship guidance provided here.

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/csdm-implementation/c...

 

 

Note : Remember, this is only suggestion. Most likely things are going to match with your infra. However, it would be best if you could cross validate this relationship mapping with the Infra team members whoever is managing the resources in Cloud or On-Prem to ensure what you are creating is correct.

Hope this helps.
Let me know if it worked.

Regards,
Vikas K

@VikMach Thank you for your response. Could you please confirm if I need to create the relationships in this way for each configuration item individually, or is there a way to generate the mapping for all items at once? Also, in the screenshot you shared, I noticed the suggested relationship option — but where can I find the option to actually create the relationship?

@Vijay Kumar4,
To create the relationship you need to create them in cmdb_rel_ci table. See example snip below.

VikMach_0-1758642484190.png

 

As you are doing it manually, yes you will have to do it for all CI's because there are different classes. (I don't know how many classes you have at the moment.) 
But you can achieve it quicker if you do it in the Excel sheet first and then upload it through transform map. Don't worry even if it goes wrong for any CI, you can correct the relationship anytime you think is not looking right as per your infra. There is a check box that shows your Suggested relationship which I highlighted earlier in my first reply.  

 

 

VikMach_2-1758643227577.png

 

VikMach_1-1758642988193.png



Regards,
Vikas K