Skip Ribbon Commands
Skip to main content
brite global home


Microsoft Dynamics CRM 2013 Extensibility
Client SDK Enhancements

In the upcoming release of Microsoft Dynamics CRM 2013, many new client SDK functions have been added. Some of these include the client class, which allows retrieving the type of client and and client state that the application is in, and due to the fact that the isOutlookClient and isOutlookOnline functions have been deprecated.

The getAuthenticationHeader and getServerUrl have also been deprecated in Microsoft Dynamics CRM 2013.

The Xrm.Page.Data received new properties and methods which include the getIsValid to do a validation check of the data on the form, the refresh method, the save method and the setFormDirty method. Although the will still work, the method provides callback functions after the save operation.

The Xrm.Page.ui received the setFormNotification and clearFormNotification for handling the form notification, since doing form notifications with the document object model is no longer supported.

The Xrm.Page.ui.Control received the following new Properties and methods which include setNotification and clearNotification which set notifications for individual controls, setPricision for numerical attributes, setAllDay and setShowTime for DateTime controls and addCustomFilter, addPreSearch and removePreSearch for lookup controls.    

The Xrm.Utility, which was introduced in CRM 2011 Update Rollup 8, includes the openWebResourceDialog, which opens an HTML web resource as a dialog.

Microsoft Dynamics CRM 2013 Client SDK Enhancements
Custom Process Actions

The standard Microsoft Dynamics CRM functionality can not be extended by adding custom system messages that are associated with request and response classes. These custom messages are called actions. In CRM 2011, actions were only available using the web service calls.

Actions will allow adding new functionality to the organization web service or to combine multiple web service calls into a single request. The following are the basic requirements for creating actions:

​Actions are implemented using a real-time workflow that is registered to execute at stage 30 (core operation) of the execution pipeline. Unlike workflows, actions do not support a scope where execute is restricted to user, business unit or organization.
​Actions support input and outoput argument types. When these arguments are added to an action, they are included in the message request and response classes.
​Actions open a range of possibilities for business analysts and developers. With actions, developers can perform operations such as Create, Update, Delete, Assign, Set Status, referred to as messages, which are based on actions taken on an entity instance. The process can perform multiple actions on a single record, such as Create the record, Update the record and finally assign the record to the appropriate user or team.
​Each action step is defined by the capabilities of the entity, not the business process. Actions provide the ability to define a message that matches the operation that has to be performed on the business. These messages are driven by a process or behavior rather than what can be done on the entity, so they can correspond to message such as Convert, Schedule, Approve or whatever action has to be performed.

Deprecated Features

The Microsoft Dynamics CRM 2007 service endpoint extensions was deprecated in Microsoft Dynamics CRM 2011. Extensions that will be using the 2007 endpoint will not be supported and will not work in the upcoming release of Microsoft Dynamics CRM 2013. The 2007 endpoint was superceded by the WCF/REST endpoint in Microsoft Dynamics CRM 2011. The 2011 endpoint will be supported in Microsoft Dynamics CRM 2013 for backwards compatibility.

The ISV folder which was deprecated in CRM 2011 will not be supported in Microsoft Dynamics CRM 2013.

Microsoft Dynamics CRM 4.0 style Plug-ins and custom workflow activites will not be supported in Microsoft Dynamics CRM 2013.

Microsoft Dynamics CRM 4.0 style scripting, which exposed the global functions and form objects to form scripting with JavaScript will not be supported in Microsoft Dynamics CRM 2013. These scripting objects and functions will be removed in Microsoft Dynamics CRM 2013, and all for scripts for the next release should use the Xrm.Page and Xrm.Utility object models. Writing JavaScript code that modifies the Document Object Model is not supported and any scripts using CRM application page DOM elements will break.

Several tools are available to help with the upgrade and check for unsupported features are available. These tools include the Legacy Feature Check Tool for on-premise customers and the Custom Code Validation Tool which detects references in code to the crmForm API.

Ribbon Command Modifications

The ribbon command infrastructure has been modified in Microsoft Dynamics CRM 2013, as there ribbon has been replaced by the command bar. The following list contains the controls that are still available on the Command Bar: Button, CheckBox, Flyout Anchor, Label, Spinner, Split Button and ToggleButton.

The ColorPicker, ComboBox, DropDown, Gallery, GalleryButton, InsertTable, MRUSplitButton and TextBox are not longer supported and will not work. The Dropdown control will automatically convert to a flyout anchor and the MRUSplitButton will automatically convert to a SplitButton control.

Microsoft Dynamics CRM 2013 Ribbon Commands


Like us on Facebook, add us to your LinkedIn network, view our videos on YouTube or subscribe to our blog. Facebook Linked In You Tube Blog and RSS
Powered By SharePoint Online