I recently answered a question about how to update the owner of a record in Unified Service Desk for Microsoft Dynamics CRM. I thought the question was really good so decided to do a quick blog post with my answer.

The question was about wanting to set the owner field, say from an agent script to assign the owner of the currently selected record to the current user.

To do this you’d create an “UpdateEntity” action. (From you Global Manager)

Assuming the entity you wish to change the owner on is in the current context the action I’m showing below in the debugger would do the trick. If the entity isn’t in the context you can always replace $Context with the required entity name.

Id=[[$Context.Id]]

LogicalName=[[$Context.LogicalName]]

ownerid = EntityReference(systemuser,[[systemuser.systemuserid]g])






 

Hopefully this is a simple example of how to change the owner of an entity and you can adapt this for your own purposes. J

7 responses to “USD – Update Owner”

  1. Hi, don’t you think this can also be done by simply clicking the “Assign” button through ribbon, whose access we often provide to agent [ As hiding a navigation bar is logical but restricting access of ribbon can abide the agent from doing, what he ought to do, (might be I am wrong in some cases).] Also it’s depend on the security role of user which work same in Dynamics CRM & USD.

    Like

    1. I agree you can simply use the assign button! This is just another option.

      If “all” you want is an assign button logic that that is best done from the CRM form.

      But it might be useful if you wanted to group several actions into one step. With changing the ownership being just one of them.

      Or maybe the ownership could change automatically based on some other logic.

      I think this could be useful in some circumstances.

      Like

  2. Please also share your experience regarding scenarios of CRM workflows

    Like

    1. What do you have in mind for workflow scenarios?

      Like

  3. Neil,

    You would only want this to run once, so say a customer record pops through CTI then it assigns the record to the current agent, if there is a second call to this customer record by a different agent we wouldn’t want it to fire, so would an execute on expression true come into play the second time?

    Thanks
    Una

    Like

    1. If you want the action to run once or maybe never if the entity is already assigned to the current user you could simply add a condition to compare the onwer from the context with the usersystem user.

      Like

Leave a comment

Trending

Website Powered by WordPress.com.