Change color of service calendar timeblock appearance in CRM 2013

The project I was working needs the service calendar feature in CRM 2013 and the business needs to customise the color of appointment based on the status.

Looked into the CRM 2013 SDK help file and discovered the way to achieve this, but the content was probably hasn't been updated for CRM 2013 due to UI change to flat style.

So, here is how to do it:

 1. Create a new webresource of CSS type.
2. Set the Display Name to 'AppointmentBookConfig'.
3. Open the Text Editor and place the new CSS style in the content text box. Use the following format to define the new color.

div.ganttBlock[entityname]Status[statuscode]
{
    background-color: #FFC251;
}

 For example, for Appointment with Free status:

 div.ganttBlockappointmentStatus1
{
    background-color: #FFC251;
}

4. Publish and refresh the Service Calendar screen. You should now see the updated color of appointment timeblock.



Another tip, the CSS class is case-sensitive and must match the code specified in CRM website. You can find the file at this location C:\Program Files\Microsoft Dynamics CRM\CRMWeb\SM\Gantt\style\GanttControl.css.aspx. Open the file in text editor or Visual Studio if you have, you can find the exact CSS class name to override and specify it in the AppointmentBookConfig CSS webresource.

Comments

Post a Comment

Popular posts from this blog

Request not supported new_xxx when calling Custom Action via WebApi

Image
Using CRM 2016 Online, you can create custom Action to execute custom business logic to meet your specific business requirements leveraging the workflow-like configuration window to define the business logic rather having it written in the code. The custom Action can be called via CRM WebApi, and I encountered the following error whilst working on one of the projects. 'Request not supported new_xxx' Whilst there could be different causes to the error, one that occurred in my case is because the Unique Name has been changed after it was created. The initial name was too long, hence, shortened afterwards. However, the new name is not re-generated in the API metadata. Rather than re-creating the custom API, you can find the original name before it was updated by inspecting the API metadata which you can view at the following Url. https://[organization uri]/api/data/v8.0/$metadata   Simply download the file and open in a text editor, you can search for the custom Act
Read more

Error in workflow sending email: "You cannot send email as the selected user."

Image
I have a workflow which sends notification email from a dedicated CRM account, eg. email reminder when a contract is reaching its expiry date. The following error occurred when executing the workflow: "You cannot send email as the selected user. The selected user has not allowed this or you do not have sufficient privileges to do so." To resolve the error, there are two things to check: a. The dedicated CRM account must allow other users to send email on its behalf. Login to CRM webclient as the user, Go to Options -> Email tab, then tick the option 'Allow other Microsoft Dynamics CRM users to send email on your behalf.' b. Any other users executing the workflow must be given the privilege to send email on behalf of other user. Go to Security Role, under Business Management, tick the 'Send Email on behalf of other user'.  However, I feel reluctant to allow most, if not all, users the ability to send email on behalf of other users as it
Read more

Field Security Profile Error

Image
Seems to be a bug with Dynamics CRM 2013 (On Premise UR3), Field Security Profile Error occurs when user creates/saves new record by clicking on Save button, then saves more changes to the record while remain on the same screen. The error does not occur on subsequent updates if the user navigates away or closes and reopen the record. The entity has a field level security enabled field of Two Options field type, and a custom form with the custom field placed on the form. The user does not have any access to the field, and uses the form which does not have the custom field. User will receive similar error as per below: Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: User with ID 04b6b312-7d65-e411-82f6-005056a03354 does not have Update permissions for the new_securefield attribute in the account entity. The accountid of the record is f919
Read more