There is a JavaScript error in your browser console - Unhandled exception in GlideAjax

[NG8]

Getting the error on the Catalog side. This is the only Catalog script for that catalog item. 

function onChange(control, oldValue, newValue, isLoading) {
// if (isLoading || newValue == '') {
// return true;
// }
// var id_change=g_form.getReference('Submitted_For_Name',getUserID);
// function getUserID(id)
// {
// g_form.setValue('requested_for_user_id',id.user_name);
// }

var ga = new GlideAjax('user_details');
ga.addParam('sysparm_name','userFieldValues');
ga.addParam('sysparm_user',g_form.getValue('submitted_for_name'));
ga.getXML(simple);

function simple(response){
var answer = response.responseXML.documentElement.getAttribute('answer');
var a = answer.split(',');
g_form.setValue('submitted_for_user_id',a[2]);
return;

}
}

[NG8]

I just get a popup that says "Sending user = " and after i click OK, JavaScript error appears again. 

[vkachineni]

So the parameter you are sending is empty

ga.addParam('sysparm_user',g_form.getValue('submitted_for_name'));

Can you check the name of the form field. Any casing issue?

[NG8]

Everything looks the same. See below. That field will be empty until a user enters "Submitted for name" value. It is "On change" script. 

When i change it to "Requested by" which loads automatically because default value is set to "javascript:gs.getUserID();"  i do get a value in "sending user="

However, this time after clicking OK, i do not get get JavaScript error. Weird

[NG8]

So when i set default value for "Submitted for" variable "javascript:gs.getUserID();" i do not get the error message anymore. But this field should not populate to whoever is filling out the form, only "Requested by" should do that. 

"Submitted for" field is there if Requested by" and "Submitted for" are different. Ex. If manager is requesting access for their employee. 

[NG8 · Accepted solution]

So seems like having "Applies on Requested Items" and "Applies on catalog Tasks" checked will give you this error. After i unchecked it, the error was gone. Really odd but it worked. 

Thank you all for your assistance with this. I appreciate it. 

I am marking this as correct answer for others to see.