CI Relationships now showing up

aditimittal
Tera Contributor

3 weeks ago

I added the cmdb_ci_ip_address class to my application which is a dependent class. In my IntegrationHub ETL, in the "Add Relationships" step, I added an Owns:Owned By relationship between cmdb_ci_zos_server class and cmdb_ci_ip_address class. My ingestion of the IP Address data was successful and the relationships also showed up in the cmdb_rel_ci table. 

I wanted to show these relationships in the CI information so I made a view and added the "CI Relations(Formatter)" in the view, but these relationships aren't showing there and neither are they showing up when I open the CI in the CMDB workspace. 

If anyone knows how to resolve this, please let me know, thanks! 

0 Helpfuls
  • 483 Views
1 REPLY 1

vaishali231
Kilo Sage

3 weeks ago

Hey @aditimittal 
Since the relationship records are getting created successfully in cmdb_rel_ci, the IntegrationHub ETL mapping and the Add Relationships step appear to be working correctly.
The issue is most likely related to how cmdb_ci_ip_address is handled/displayed. cmdb_ci_ip_address is a dependent CI class, and dependent CI relationships may not always appear in the standard CI Relations formatter or CMDB Workspace relationship view, even though the relationship exists in cmdb_rel_ci.


I would suggest checking the following:


Confirm the relationship exists in cmdb_rel_ci
Verify that the record has:
Parent: cmdb_ci_zos_server
Child: cmdb_ci_ip_address
Type: Owns::Owned by
Check if the relationship is filtered from the formatter/workspace
Some CMDB views/components may exclude dependent CI classes from the standard relationship display to avoid showing supporting/dependent records.
Validate the class configuration
Go to CI Class Manager and review the configuration for:
IP Address [cmdb_ci_ip_address]
Check whether it is configured as a dependent class and whether there are any relationship/display rules affecting it.
Test with a non-dependent CI class
Create the same type of relationship from cmdb_ci_zos_server to a normal CI class. If that relationship appears in the formatter/workspace, then the behavior is specific to the dependent IP Address class.
As a workaround, if the requirement is to show IP Address data on the CI form, you can add a related list on the cmdb_ci_zos_server form based on cmdb_rel_ci, filtered where the child CI is from cmdb_ci_ip_address. For CMDB Workspace, you may need to configure/customize the workspace component or expose this through a custom related list/section.

*************************************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb

 

0 Helpfuls