In this series we have been looking at the Developer Extensions provided by the Microsoft.Xrm.Client assembly:
Part 1 - CrmOrganizationServiceContext and when should I use it?
Part 2 - Simplified Connection Management & Thread Safety
Part 3a – CachedOrganizationService
So far in this s... [More]
When CRM2011 UR 12 (POLARIS) introduced asynchronous loading of web resources, there were some unfortunate side effects caused by the load order in which the scripts were executed not being the same as defined by form customisations. If you had scripts that required a previous scripts to be loaded f... [More]
This post provides the important information you need to know in order to transition to customising the Command Bar in Dynamics CRM 2013.
1. The Command Bar is a Ribbon in disguise!
The Ribbon Bar in Dynamics CRM 2013 to a certain degree has been replaced by the Command Bar but it still exists on ... [More]
Scenario
UPDATE: With CRM2015 - the new client side process API should be used to set the current step. The following approach should be only used for setting the process to the first step.
If you have more than one Dynamics CRM 2013 Business Process Flow for a given entity users can easily change... [More]
If you use LINQ queries with the OrganizationServiceContext then understanding MergeOptions is vital. At the end of this post I describe the most common 'gotcha' that comes from not fully understanding this setting.
The OrganizationServiceContext implements a version of the 'Unit of Work' pattern (... [More]
The new Dynamics CRM 2013’s command bar has deliberatly limited space for buttons due to the ‘intentionally constrained’ user interface design. The idea being that if you limit the space for buttons, then designers will be forced to only show those that are absolutely necessary ... [More]