Skip to main content

Oddity with For loops in ServiceNow!

Not for the first time, I have noticed issues with For loops in ServiceNow

for (i=0;i<10;i++){



The loop can at times appear to get stuck and the 'i' counter stops incrementing. Having not yet got to the bottom of it, I can only assume that some other object behind the scenes is already using 'i' , or possibly several client scripts using i exist on the form, though in theory the functions should encapsulated.
The problem certainly seems to go away by replacing the above with something like:

for (i_counter=0;i_counter<10;i_counter++){



Hence, I can't say I could recommend using the 'i' variable anywhere in for loops when coding in ServiceNow!

...Watch this space, I may post more once I get to the bottom of why this happens!...


  1. maybe including var i=0 instead of just i=0 helps...
    for(var i = 0; i < favorites.length; i++) {

  2. Ran across this one. It was scoping issue - instead of
    for([var] i = 0; i<counter; i++){gs.print(i)}; enclosure helps:
    function() { var x,y,z,i; //<- all local
    for (i=0;i<10;i++){
    so the I is always local to anonymous/function rather than i's in scripts includes. HTH

    1. Good call Max, thank you. Enjoy the Knowledge18 event mate


Post a Comment

Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue'" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object