Just a heads up, Jakarta seems to handle line breaks in gs.addInfoMessage differently. I put a br tag at the end of the msg lines and it fixed the problem.

Also, we rely a lot on this functionality, especially when it comes to assignment groups. If someone asks to rename a group we use this to see what catalog items, assignment rules, scripts, etc. that will be affected. Right or wrong, there’s a lot of .setDisplayValue() going on here and it needs to be maintained.

To solve this, I created a function to check for named references if we’re checking a group. You can easily add/remove areas you need to check for named references. It’s pretty handy so I wanted to share. Added the following code before your gs.addInfoMessage(msg) at the end.

//Query for name references if it’s a group
if(current.getTableName() == ‘sys_user_group’){
var nameMsg = ‘Matching SCRIPT fields (Assignment Rules, Record Producers, Client Scripts(client, catalog, wizard), and Workflows) where this record is referenced by NAME are displayed below…‘;

nameMsg += findTableReferences(‘sysrule_assignment’, ‘script’, current.name);
nameMsg += findTableReferences(‘sc_cat_item_producer’, ‘script’, current.name);
nameMsg += findTableReferences(‘sys_script_client’, ‘script’, current.name);
nameMsg += findTableReferences(‘catalog_script_client’, ‘script’, current.name);
nameMsg += findTableReferences(‘expert_script_client’, ‘script’, current.name);
nameMsg += findTableReferences(‘sys_script_include’, ‘script’, current.name);
nameMsg += findTableReferences(‘u_workflow_script’, ‘val_value’, current.name);
gs.addErrorMessage(nameMsg);
}

And here’s the function…

function findTableReferences(tblName, column, name){
var message = ”;
var recMsg = ‘ records found’;
var workflowURLQuery = ”;
var prefix = ‘Table’;

var gr = new GlideRecord(tblName);
gr.addQuery(column, ‘CONTAINS’, name);

//for the client script table, only return client scripts and not catalog or wizard
if(tblName == ‘sys_script_client’)
gr.addQuery(‘sys_class_name’, ‘sys_script_client’);

if(tblName == ‘u_workflow_script’){
gr.addQuery(‘wfa_workflow_version.published’, true);
workflowURLQuery = ‘wfa_workflow_version.published=true^’;
prefix = ‘Workflow Activity’;
}
gr.query();

if(gr.getRowCount() == 1){
recMsg = ‘ record found’;
}

if(gr.getRowCount() > 0){
message = ‘–‘ + prefix + ‘: ‘ + tblName + ‘‘ + ‘ – Column [Column type]: ‘ + column + ‘ [‘ + ‘string’ + ‘]’ + ‘ — ‘ + ” + ‘‘ + gr.getRowCount() + recMsg + ‘‘ + ‘.’ + ”;
}else{
message = ‘–‘ + prefix + ‘: ‘ + tblName + ‘‘ + ‘ – Column: ‘ + column + ‘‘ + ‘ — ‘ + ‘NOTHING FOUND’;
}

return message;
}

Great post.

Thanks Christian, I haven’t heard of that happening before but I’ll keep an eye on it.

Thanks for the heads up! I haven’t seen this before so I’m not sure it applies everywhere but this will be good to have here just in case someone else encounters the issue.

dict.addQuery(‘name’, ‘DOES NOT CONTAIN’, ‘dl_matcher’);
dict.addQuery(‘name’, ‘DOES NOT CONTAIN’, ‘grc_risk’);

This is in case for the find record reference script to work when attempting to execute the action on Users table.

I believe its due to the base tables not being accessible for the admin user. The missing table error is also posted to ServiceNow logs.

Awesome, thanks for the update! I’ve adjusted the solution above with this fix.

In Fuji, one thing I noticed though is that addEncodedQuery in combination with addOrCondition is not working as expected anymore. The ^OR conditions seem to be ignored. One way to fix this issue is to modify line 24 (replace addEncodedQuery by addQuery):

dict.addQuery(‘reference’, ‘IN’, refTable).addOrCondition(‘internal_type’, ‘document_id’).addOrCondition(‘internal_type’, ‘conditions’);

// Test with Fuji Patch 10
var dict = new GlideRecord(‘sys_dictionary’);
dict.addEncodedQuery(‘referenceIN’ + ‘core_company’).addOrCondition(‘internal_type’, ‘document_id’).addOrCondition(‘internal_type’, ‘conditions’);
gs.log(dict.getEncodedQuery()); // *** Script: referenceINcore_company

var dict = new GlideRecord(‘sys_dictionary’);
dict.addQuery(‘reference’, ‘IN’, ‘core_company’).addOrCondition(‘internal_type’, ‘document_id’).addOrCondition(‘internal_type’, ‘conditions’);
gs.log(dict.getEncodedQuery()); // *** Script: referenceINcore_company^ORinternal_type=document_id^ORinternal_type=conditions

Obviously adding the line rec.setWorkflow(false); would help avoid query business rules.