Comments on: Creating an Alias for Reference Field Searches https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/ ServiceNow Consulting Scripting Administration Development Tue, 28 May 2024 21:23:00 +0000 hourly 1 https://wordpress.org/?v=6.8.2 By: Mark Stanger https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6996 Mon, 29 Aug 2016 18:50:32 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6996 In reply to Robert Sloan.

You should be able to use this exact same solution for any other CI type, including business services. The only step that would change is the final script (and then it would only change if the field you were referring to wasn’t ‘cmdb_ci’. If it is different, just replace ‘cmdb_ci’ with the name of your field and then have your client script run on change of that other field.

]]> By: Robert Sloan https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6995 Mon, 29 Aug 2016 18:30:32 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6995 Looking for a method to use an alias for Incident Business Services.
I was able to apply above method for using Alias’s on Configuration Items, and count about 5 steps.
Am trying to apply same method on Incident Business Services, but can’t quite get it functional.

Is there a written procedure anywhere for this?

Thanks

]]> By: Mark Stanger https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6994 Wed, 02 Sep 2015 12:00:44 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6994 In reply to Glen.

There are ways, but the only supported, documented way is explained in this SN wiki article. You can ignore the part about reference qualifiers for lists, that’s an error.
http://wiki.servicenow.com/index.php?title=Filtering_Related_List_Relationships#gsc.tab=0

]]> By: Glen https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6993 Fri, 28 Aug 2015 19:50:46 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6993 Could these be excluded from being used in related lists like “Affected CIs”?

]]> By: Mark Stanger https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6992 Tue, 21 Apr 2015 19:39:53 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6992 In reply to Stephen.

Yes! You can take the script logic above and use it in the UI policy script fields the same way.

]]> By: Stephen https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6991 Tue, 21 Apr 2015 19:30:23 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6991 Can this be done in a ui policy as well?

]]> By: Mark Stanger https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6990 Wed, 09 May 2012 22:28:30 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6990 In reply to Kate.

I suppose it could, but that could be easily circumvented just by labeling the alias CIs as such. Then you could simply filter them out in your reporting as needed.

]]> By: Kate https://servicenowguru.com/client-scripts-scripting/creating-alias-reference-field-searches/#comment-6989 Wed, 09 May 2012 21:23:31 +0000 https://servicenowguru.wpengine.com/?p=1662#comment-6989 It seems like this could cause issues around reporting. By having alias CIs included on the same CI table, wouldn’t that skew your numbers for reporting total class counts? In particular, if it were used with active servers.

]]>