Yes I have.

Doing this does allow me to select any user from the sys_user table, however there are a couple other issues with this process.

The first is that this does not update the 'requested_for' field tied to the service request. Our approvals, emails, and many references in task short descriptions, etc. all reference the 'Requested for' user tied to the RITM. We're wanting to update that field based on the field added to the form.
- I do believe it would be possible to create an 'onSubmit' catalog client script using GlideAjax to access the requested_for field on the RITM, and update it to match what is entered into the reference field we create. But I haven't done this before and might need a little guidance to get that to work correctly.

The second piece is that we are wanting to be able to submit a single request for multiple 'Requested for' users. The 'Requested For' field gives us the ability to submit a single request for multiple users, and then separate RITMs are created for each user selected. I don't believe we would be able to accomplish this with a reference field... at least not without some fancy customization.

Thank you for the help 🙂

yes, multiple users for requested for is a feature for requested for type 🙂

could you create user criteria for all active users and assign to your item?

I did test this as well, and it works, but then non-requesters are able to submit this request. We have a standard to only allow certain people to submit requests, and don't want to open that up to people who we haven't granted those permissions to.

Thank you

Hi @KirklandC 
It sounds like you’re running into an issue related to how ServiceNow controls access to catalog items through user roles and catalog item entitlements. When you try to submit a request on behalf of another user (using the ‘Requested for’ field), ServiceNow checks whether the selected user has the necessary permissions to access and order the catalog item. If the user doesn’t have the required permissions or roles, ServiceNow will show the error “Item is unavailable for this user.”

In scenarios where it’s necessary to submit requests on behalf of users who may not have direct access to certain catalog items, consider the following approaches to resolve or work around the issue:

1. Review and Adjust User Roles or Catalog Item Entitlements

- Catalog Item Entitlements: Check the entitlement conditions on the catalog item to ensure they’re not overly restrictive. You might be able to adjust these conditions to not check for specific roles if the item is ordered on behalf of another user.

- User Roles: Ensure that either the item doesn’t require specific roles that the ‘Requested for’ user lacks, or consider adding a role to users that grants the minimum necessary permissions.

Note: Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning ‌‌
Thanks & Regards 
Deepak Sharma