XRM Stuff

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.ganttBlockappointment Status1 {     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 c...

Very useful list of statuscode and statecode. http://mostlymscrm.blogspot.com.au/2012/06/entity-statecodes-and-statuscodes.html

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...

Installed CRM 2013 On-Premise, built in report works fine but custom report created via Report Wizard is not working. Error detail below: Log Name:      Application Source:        MSCRMReporting Description: Report render failure. Error: An error has occurred during report processing. (rsProcessingAborted) To fix this, simply add the following SPN: setspn -s http/[crm server name] [domain]\[crm service account] for example: setspn -s http/crm ad\crmsvc

Just discovered a bug in top navigation link in CRM Online 2013. The drop down arrow to view the associated record disappears when the name of the record is too long. Long name, the drop down disappears: Short name, the drop down shows up:

Seems to be a bug in CRM 2013 Online RU1 that generic error occurs when defaulting a lookup field value using parameters on form. I had the following code:        var parameters = {};              parameters["new_customid"] = "621E9F4C-AD5C-E311-84F4-D89D67768C0C";              parameters["new_customidname"] = "Record Name";        parameters["new_customidtype"] = "new_customentity";        Xrm.Utility.openEntityForm("new_anotherentity", null, parameters); to pre-populate the 'new_customid' lookup field but generic error occurred. Searched on the web for a bit and found Form Query String Parameter Tool, and noticed that the last parameter ["new_customidtype"] is not required. However, CRM SDK states that this last parameter is required. Nonetheless, removed the last parameter and it works now.

Encountered more issue when deleting a managed solution from Dynamics CRM 2013 Online. I attempted to delete the solution from the usual location, ie. navigate to Solution, then click on Delete for the solution selected. The system went through the component dependency check process as usual and found dependent components of SDK Message Processing Step. Error as shown below. I then checked the plugins and its steps. I removed all of them using Plugin Registration Tool and tried to delete but same error occurred. It turns out there are some Processes (could be Workflow or Business Process) which have the reference to those fields. Once I deleted those processes, the solution was then successfully deleted.