ehussey

I also ran into this when trying to create tickets via REST. The error showed up when I tried to use a "username" field to identify a client instead of "id". It also got picky about the case of the "id" parameter and it didn't like strings getting passed to numeric fields, ie. "id":"12015" vs. "id":12015 Here's an example…

Apologies, I didn't look at the spec in enough detail I know the documentation doesn't list room as one of the editable asset fields, but it does show up when pulling asset details from the API "room":{"id":102,"type":"Room","roomName":"Test Room"} I wonder if the API would accept the field even though it's not in the…

It looks like you can include a Location object when creating an Asset; does that look like something that would do what you want?

I've accidentally ended up writing code that tried to send a POST request multiple times, so that's one possibility; you might want to trace and see what your code is actually sending over the network. You might have some Action Rules or Approval Processes that are getting applied on ticket creation that trigger more…

You should be able to turn on "Include Room Assets in Client Asset List" and "Ticket Must Use Assigned Asset" in Setup -> Requests -> Options. It looks like you can require users to choose an asset by turning on Setup -> Request Types > [Request Type] > Model Required

20 machines out of ~640 sounds like it could be a problem with WMI. Microsoft has a WMI diagnostics tool (A New Utility for Diagnosing and Repairing Problems with the WMI Service ) you could try running on one of the computers that doesn't get discovered