Hello,
I have had the same issue and looked into a temp fix with some scripting.
This worked for me...pieces taken from various posts.
If Outgoing, I want the FROM field to have the current user
If InComing, I want the TO field to have the current user
So, create a new .js file with this function in it:
function SwapIncomingOutgoingUser(control)
{
//get direction of call
var direction = control.getEventSource().getValue();
//get current user name and ID
var userId = Xrm.Page.context.getUserId()
var userName = Xrm.Page.context.getUserName();
var partylistarray = [];
partylistarray[0] = {};
partylistarray[0].id = userId;
partylistarray[0].name = userName;
partylistarray[0].entityType = "systemuser";
//NOTE: you might need to change the entityType to that which is being looked up... eg: account or contact
if (direction == 1)
{
Xrm.Page.getAttribute("to").setValue(partylistarray);
Xrm.Page.getAttribute("from").setValue(null);
}
else
{
Xrm.Page.getAttribute("from").setValue(partylistarray);
Xrm.Page.getAttribute("to").setValue(null);
}
}
Load that into the form with any other scriptfiles that are also being loaded.
In the OnChange event on the Direction field/control, reference the method [SwapIncomingOutgoingUser] in your .js file and be sure to check the box: Pass execution context as first parameter.
Save and publish and try adding a phonecall and it ought to work...
Bear in mind, MS are supposed to be issuing an update as it is a known error but this is a work-around for now.
Hope that helps!
