CMDB Relationship editor "save" & "Save and Exit" buttons greyed out

o_jay
Tera Expert

Hi Everyone,

I have a brand new Washington DC PDI instantiated this morning (0900 CET, 20-05-2024).  When I try to use the relationship editor (on existing and newly created CIs), the "Save" and "Save and Exit" buttons are greyed out.

I have checked all existing similar documentation (links below) and it appears there are no bad records in the cmdb_rel_ci table, and I've confirmed my user has all appropriate roles (itil_admin, admin, etc.).

Has anyone seen similar - where should I look for issues other than in the relationship table?

Thanks!

 

Prior reading I've checked against:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0696861

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0687679

https://www.servicenow.com/community/developer-forum/save-save-and-exit-button-getting-disabled-for-...

 

1 ACCEPTED SOLUTION

o_jay
Tera Expert

Following the documentation here exactly resolved my issue - looks like some combination of what I was doing was not creating valid relationships, so it couldn't be saved.  So ... working as designed, and my fault.

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...

View solution in original post

3 REPLIES 3

AJ-TechTrek
Giga Sage
Giga Sage

Hi @o_jay ,

 

Even i just tried with my Washington DC Release PDI , I am facing the same issue, Might be there is some issue with Relationship editor.

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thanks

Ajay Kumar

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

I have just tried with a Vancouver instance as well ... same issue.  Is there a way to raise this to a support team who can investigate?

o_jay
Tera Expert

Following the documentation here exactly resolved my issue - looks like some combination of what I was doing was not creating valid relationships, so it couldn't be saved.  So ... working as designed, and my fault.

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...