Requested_for is showing incorrect value on RITM

[robinpaul]

Hi All!

I have this issue when users submit requests for multiple people at once by using 'add to cart' button, which does not work properly.

For example, I need to submit " Software Request access"catalog item request for 10 different people. In this case, I would select catalog item variables for 1st user, then press 'add to cart' which would add my desired item to my cart. I would then stay on the same form and change variable for access to 2nd user, 'add to cart', then 3rd user, 'add to cart', etc. Once I select last user I would 'order now' all 10 access requests at once. So far everything is working well. When I order 10 items, this actually gets logged as one request (REQ) and 10 different requested items (RITM's).

However (here is the issue), since REQ supports only single 'requested_for', all RITM's requested for' gets copied over with the last selected user's name. Therefore, all 10 items end up being submitted for one same person rather than 10 different users.

Did anyone experience the same kind of issue? What did you do to solve this? Did anyone create anything for allowing users to submit multiple requests for multiple users at once?

Any help would be appreciated.Thanks in advance

[CharlesGriff]

HI Robin paul

I have had to work with similar difficulties I ended up creating a new requested for field on my RITM table and just hiding/removing the default requested for field that gets populated from the request table as this will always default to the person who opened the initial request, so your request will have the person who logged the request as the requested for but on your RITM you can then have different requested for people in your new field. you can hide the field by editing the list layout and just removing it this will not delete the field but just not display it.