Skip to main content

ServiceNow: add an OR condition to GlideRecord if the initial lookup fails

add an OR condition to GlideRecord if the initial lookup fails




var queryField='number';
var rawField='INC0010001'; //--un-comment to test EQUALS
//var rawField='5'; //--un-comment to test LIKE
var tableName='incident';
var res= getReferenceFromRaw(tableName, rawField, queryField);
gs.print('result='+res);

function getReferenceFromRaw (tableName, rawField, queryField) {

// return if raw field is empty
if (rawField == '') {
return '';
}

try { //--
var grTable = new GlideRecord(tableName);
grTable.addQuery(queryField, rawField); //--EQUALS query

grTable.setLimit(1);
grTable.query();
if (grTable.next()) {
//--gs.info('EQUALS');//--not advisable to uncomment if large volume of logs written
return grTable.getUniqueValue();

} else {
//--else statement
//--see https://developer.servicenow.com/dev.do#!/reference/api/tokyo/server/c_GlideRecordScopedAPI
//-- add/applyEncodedQuery function
grTable.initialize();
grTable.addEncodedQuery(queryField + 'LIKE' + rawField); //--CONTAINS query

grTable.setLimit(1);
grTable.query();
if (grTable.next()) {
//--gs.info('CONTAINS');//--not advisable to uncomment if large volume of logs written
return grTable.getUniqueValue();
}
}
} catch (ex) {
//--gs.logError('error:'+ex.toString(),'getReferenceFromRaw');//--not advisable to uncomment if large volume of logs written
}

return;

}


ServiceNow 


Comments

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...