Best Method To Get A Count On Data In A Catalog Item?

[Casey23]

Hello! I need to create a catalog item that will be replacing our lost/damaged device form. The goal is that after the user submits the request, IT will be able to report off of the data to see how many of each type of device were lost or stolen over a time period (last year, last month, etc.). I'm trying to find the best way to accomplish this. Users could submit a request that has a single computer that was damaged, or they could submit a request with multiple damaged computers, workstations on wheels, monitors, and any other devices we decide to add. The part I'm struggling with is how can I design the catalog in a way that we'll be able to report on it successfully?

As an example, I was thinking about using a lookup select box where I could have 5 entries for "Computer" in a variable reference table. The thought being that no one should be submitting the request with more than 5 damaged/lost PCs. The value of computer would be 1, so if I had 2 requests that were submitted where "Computer" was selected only once in the first RITM, but then it was selected twice in the second RITM, I could get a count of the value and report 3 computers. I'm not seeing a way to get the value in the report though. Rather when I select the "damaged device" variable, I see "Computer" which also shows up in the report instead of the value.

Has anyone done something like this before, and if so, what thoughts do you have?

[Kieran Anson]

I would move away from viewing the request record(s) as needing to hold your reporting data - but focus on those being your process drivers to fulfill what needs to be done as part of your lost/stolen device process.

These asset records should have their state changed (either manually or automatically using flow designer). OOB the "Missing" state has substates of "Lost" and "Stolen". I'd also create a new many-to-many table to link RITMs to assets so you have a data link

[Casey23]

That makes sense, but we're actually not looking to tie in with actual assets or CIs at this time. Mainly because a lot of our devices aren't currently in ServiceNow as assets/CIs since we sometimes track them as consumables. It's not ideal, but that's where we're at right now. So basically what we're trying to do is figure out what was damaged/lost, how many of those items there were, and how can we track them over time.