Sonoma Partners Microsoft CRM and Salesforce Blog

Dynamics CRM - Managing Appointment Status Reasons

If you have ever tried adding, updating or deleting Status Reasons on the Appointment entity for any non-Open values, you’ll know that the Status selector is disabled as shown below.  This prevents Admins from being able to easily modify Status Reasons for Completed, Canceled and Scheduled states. 

image

Fortunately we can still insert, update or delete Status Reasons using the API.  To insert a new Status Reason value there is a special API method that is different from inserting a regular Option Set value.

Below is an example of using the InsertStatusValueRequest which allows you to specify which StateCode the new value will be associated to.  In this sample we are creating a new value, “My Canceled Value”, for the “Canceled” StateCode.

var insertStatusValueRequest =
        new InsertStatusValueRequest
        {
            AttributeLogicalName = "statuscode",
            EntityLogicalName = Appointment.EntityLogicalName,
            Label = new Label("My Canceled Value", 1033),
            StateCode = 2 // Canceled
        };

OrgService.Execute(insertStatusValueRequest);
 
 

To update the newly added Status Reason value, there isn’t a specific request for Status Reasons but we can use the same request for regular Option Sets.

var updateOptionValueRequest =
        new UpdateOptionValueRequest
        {
            AttributeLogicalName = "statuscode",
            EntityLogicalName = Appointment.EntityLogicalName,
            Value = 100000000,
            Label = new Label("Updated Option 1", 1033)
        }; 

OrgService.Execute(updateOptionValueRequest);
 
 

Same goes for deleting a Status Reason value.  We can use the same request for regular Option Sets as well.

var deleteOptionValueRequest = 
        new DeleteOptionValueRequest {
            AttributeLogicalName = "statuscode",
            EntityLogicalName = Appointment.EntityLogicalName,
            Value = 100000000
        };

OrgService.Execute(deleteOptionValueRequest);

 

Hopefully in the future Microsoft will enable the Status selector as there doesn’t seem to be an apparent reason for it to be disabled.  This will allow non-developer Admins to be able to easily manage Appointment Status Reasons without using code.

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM 2013