GlideForm don't set list collector value properly with GlideAjax response

jerrypeng02 · ‎08-29-2024

The current problem is: I want to set the list collector value with user list I get back from GlideAjax response in my onChange catalog client script. The `userList` I got back and display on the form is actually the same as my hardcoded list for user sys ids. But when I set the hardcoded value to the users field of the form, it only appears 2 users on the right of the slushbucket. What is going on and how do I resolve this problem?

Below are the code:

function onChange(control, oldValue, newValue, isLoading) {

if (isLoading || newValue == '') {

return;

}

var gUrl = new GlideURL();

gUrl.setFromCurrent();

var businuessLocationId = gUrl.getParam("sysparm_parent_id");

var responsibilityType = newValue;

var ga = new GlideAjax('GetResponsibilityMemberUsers');

ga.addParam('sysparm_name', 'getUsers'); // Function name should be provided

ga.addParam('sysparm_bl', businuessLocationId);

ga.addParam('sysparm_type', responsibilityType);

ga.getXMLAnswer(callback);

}

function callback(resp) {

var userList = resp;

g_form.clearValue('users');

// g_form.setValue('users', userList);

g_form.addInfoMessage('users ' + userList);

g_form.setValue('users', '1d6705835b2506100c7609f8e281c73f,4a826bf03710200044e0bfc8bcbe5d7f,36d581035b2506100c7609f8e281c7de,56826bf03710200044e0bfc8bcbe5dca');

}

Brad Bowman · ‎08-29-2024

If the property doesn't exist the results are limited to 100. Create a property with that name and set it to 200, or 500, or whatever. Updating the filter, either via reference qualifier or a script will limit the number of records on the left, thereby ensuring that the intended records are present. In this case, it seems like it would be best to use the same string of sys_ids returned by the GlideAjax, then you would precede it with 'sys_idIN' before using it to update the filter, then lastly update the variable value:

function callback(resp) {
    var userList = resp;
    var varName = list_collector_variable_name;
    var filterString = 'sys_idIN' + resp;
    try{
      var myListCollector = g_list.get(varName);
      myListCollector.reset();
      myListCollector.setQuery(filterString);
     }
     //Revert to Service Catalog method
     catch(e){
      window[varName + 'g_filter'].reset();
      window[varName + 'g_filter'].setQuery(filterString);
      window[varName + 'acRequest'](null);
    }
    g_form.setValue('users', userList);
}

View solution in original post

Brad Bowman · ‎08-29-2024

I think this issue is that the values must first be in the 'Available' list before they can be 'selected' when doing this via g_form. The system property glide.xmlhttp.excessive limits the results of slushbuckets system-wide, so in this case not every user is initially available to be selected. Increase the value of this property so that more/all records are 'available'.

Depending on the number of records in the list collector table, you might also want/need to update the filter before setting the value, so that all of the intended records to be selected actually are 'available'. See this article for tips on dynamically updating a list collector filter

https://www.servicenow.com/community/itsm-articles/advanced-filtering-of-list-collector-variables-de...

jerrypeng02 · ‎08-29-2024

Thanks for your reply! But I tried the set the hardcoded value after ga.getXMLAnswer(callback); and then all 4 users will appear. Do you know what specific system property it is for solving it?

Brad Bowman · ‎08-29-2024

I've updated my reply with the property name. I gathered from the original question that only two users appeared whether the value was set by a hard-coded list or a value returned via GlideAjax.

jerrypeng02 · ‎08-29-2024

I checked the sys properties but there is no such property called glide.xmlhttp.excessive. And for updating the filter before setting the value, are you saying on the left side of the list collector, I should probably not display all available users but part of them after filtering?