Creating a suggested relation of global scope type in non-global application scope throws an error and prevents the record to be deleted - Known Error

Creating a suggested relation of global scope type in non-global application scope throws an error and prevents the record to be deleted Description When creating a suggested relation in non-global application scope, if the relationship type is in global scope, then below error is thrown: The 'Suggested Relationship' record is in application 'Active Directory', but its 'CI Relationship Type' parent record is in application 'Global'. The record and its parent must be in the same application.

However, even if the error is popped, the suggested relation is still created, and can not be deleted via UI, as the delete button does not work.

Steps to Reproduce

1. Change application scope to "Active Directory"

2. Create a new Suggested Relationship with below choices: Base class - .Net Application Relationship - Allocated from (parent) Application - Active Directory Dependent class - A10 Load Balancer

3. Submit and observe the error: The 'Suggested Relationship' record is in application 'Active Directory', but its 'CI Relationship Type' parent record is in application 'Global'. The record and its parent must be in the same application.

The suggested relation between .Net Application and A10 Load Balancer is still created and the delete button on this new relation does not work.

Workaround This problem is fixed in all currently supported releases. Review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.

If you would like to delete the Suggested Relation created, identify its sys_id and use the below background script:

var gr = new GlideRecord('cmdb_rel_type_suggest'); gr.get('f69f3055db424450a33ae64305961913'); //this is the sys_id of the suggested relation gr.deleteRecord();