Ping ​@zachary.king ​@Daniel Söderlund ​@Roxwell 

Hard to do it in a good way as you can’t loop assets. 

A way could be that you create a new asset on the fly using API in an workflow. 

In the form you have option for how many. 

Create a new asset called something like this “”Hardware name” - “loaner name” - “how many xx” - “Ticket ID“ associate it to the ticket and the requester. 

Have a date field where the requester can set pickup and return date. Then you can have a scheduled workflow that reminds the support they need to check the HW and you can remind the requester if they aren’t returned. 

When they are returned and you checked all are ok can close/resolve the request and delete the asset created. 

If you like to add the actually asset to the ticket you can do that manually 
Just keep the asset id for the one you created in a custom field so you can delete it at the end. 

 

Hello ​@cameronm if you are not concenred that the requester selects specific devices, you could just have a dropdown in the form to identify the device type, and a field to have the user identify the quantify of devices they need. Then have your agents use the fulfillment process to allocate the desired number of assets to the ticket. I understand this would be a manual effort for the agents but as ​@Daniel Söderlund mentioned, you can’t loop over assets in a service item.