Auto assignment toggle not working as intended

Any progress on this? Had the same question.

Ignore that, I figured it out! ^

Would you mind sharing your solution/approach that you used for this issue. Thanks

Sure thing! I initially used the Fresh service Discovery agent thinking it would auto assign the used by field based on the “Last Logged In” field but turns out you need the probe as well. Since we don’t have an on Prem AD we couldn’t even set up the probe. 

The work around I used was creating a workflow that gets the Last Logged user and puts it into the Used By field of the asset.

In order to do this you have to make a Custom Object and create records of all the requesters you expect to be assigned to assets. I just exported all of our requesters, set them up how I needed, and imported them into my custom object. For the custom object you need the Name of the user that the FS agent pulls and the requesters email. For example: Name: “FirstLast” or “BillyBob” is what the agent will pull for the users name and then that requesters email to match the user flast@example.com or bbob@example.com.

Then in my workflow I set my trigger to be when the asset is updated, it reads from my custom object, GETs that requester in FS by the email in the custom object record, parses that data, and PUTs the requester in the Used by field.

                                 Here is the endpoint I used for my Get web request

                     When you parse that data make sure you enter a 0 here for requester id

                         Here is the endpoint and body I used for my Put web request

This is how ours works, still trying to find a better way to update my custom object when we have new requesters so I don’t have to manually add them into my custom object (if anyone has some insight on that I would really appreciate it). But every time the FS agent pulls a new requester name on a device it will update to that user (we have an issue with people signing in to different computers lol). 

If you run into any issues just let me know and I hope this helps!

You're on the right track! Using a workflow with JSON and Web Requests could definitely help automate updating the "Used By" field based on "Last Login By." You might not need a probe at all if the data exists in your system. Look into setting up a custom workflow that pulls the login data via API and maps it to the asset's "Used By" field. It could save tons of manual work across divisions.