There might be a more efficient way, but a simple way would be to use my code above, but then add to a counter variable inside of the while loop instead of printing out the results. Right before the while loop you would initialize your counter variable at zero then right after the while loop you could print out your results.

I see what you’re saying. It’s a shame, but there is no such thing as a ‘NOTIN’ operator, or anything similar. I think what you’ll need to do is do several ‘!=’ operators with multiple ‘ANDs’ as separators. It will accomplish the same thing but will look a bit uglier. For this situation, you could probably just hide the filter completely and avoid the ugliness as well.

That got me a lot closer to what I’m after but I can’t seem to use a NOTIN filter on a list collector. It works just fine if I tell it to return all results where sys_idIN, that is, it shows me the groups of which I’m already a member. If I change that to sys_idNOTIN then the filter doesn’t show up on the list collector at all and it returns all results.

If I use the technique you described to push the groups of which I’m already a member to the right side, then how will the recipient of the catalog task know which groups I was already in and which I’m requesting now? I guess they could check themselves but that seems like extra effort.

I don’t think so. I think what you could do in that case would be to query for (and display) the groups that the user was already a member of and then move them to the right side of the slushbucket. That would leave the remainder in the left side. It’s not a simple scripting task, but could be done. Here’s a separate post I wrote that might get you started.

https://servicenowguru.com/scripting/client-scripts-scripting/move-list-collector-options/

Another option would be to set the filter of the list collector to filter out the groups that the user is already a member of, similar to a reference qualifier. You would need to query the sys_user_grmember table and then return a list of sys_id values of the groups the user already belonged to. Then you could set the list collector filter as shown here.

https://servicenowguru.com/scripting/client-scripts-scripting/changing-filter-list-collector-variable-client-script/

Hey Angela, Welcome! I wrote a post to cover most of the common GlideRecord calls. It’s got examples of all of the common tasks. You can also ask on the ServiceNow forums for help.
https://servicenowguru.com/scripting/gliderecord-query-cheat-sheet/