Microsoft has recently released Dynamics CRM 2016 that has whole bunch of new and exciting features. One of the features that will help the Developers is around Solution Management.
In previous versions of Dynamics CRM, adding an entity to a Solution would add all the components. But, in Dynamics CRM 2016, Developers would be able to select the specific components while adding it to a Solution –
This features ensures that only required components are added and the size of the solution is minimal.
It is important to validate your current CRM system before upgrading to CRM 2013. Be sure, to run the CRM 2013 Custom Code Validation tool (available on codeplex)
It will detect issues in the custom web resources that will no longer work after the upgrade is completed. The most common issues that this tool targets are –
- CRM v4 client SDK calls
- CRM 2007 end points
- Common DOM manipulations
Running this tool before upgrade will enable you to identify issues and fix them prior to your scheduled upgrade so that your upgrade process can run smoothly.
Here I have highlighted the new features on offer and what benefits they will bring to businesses.
New user interface – The new user interface in CRM is clean and minimalistic. This should help staff be more productive and effective, using the latest form enhancements such as new layouts, replacement of the Ribbon with a minimalist command bar, auto-save, quick-create records, touch-friendly navigation, mapping integration, enterprise social integration and the reduced number of pop-ups.
Process Agility –The Process Agility feature can be used to model any number of business processes so that CRM is tailored specifically for your organisation. For example, new insurance policies versus insurance policy renewals, or a technical issue versus a customer complaint issue. At each stage, you can enforce that certain mandatory fields must be completed before staff can progress to the next stage. All of this functionality is available through an easy-to-use process modelling tool, reducing the dependency on custom development work.
Mobile Apps – The new mobile app allows access to CRM from a Windows 8 tablet or iPad. No additional training for the app is required as the reimagined interface, process agility and business rules are integrated seamlessly across web and mobile devices.
Server side synchronisation of Contacts, Tasks, Phone Calls and Appointments – Staff can directly synchronise information between CRM and Exchange using mobile devices to stay up-to-date at all times without the need for a third-party product or laptop. For example, staff will now see calendar appointments in their phone if they are scheduled to work on a service activity.
Enterprise social integration – Both CRM and non-CRM users can access key CRM information through Yammer. For example, businesses can automatically post to Yammer when an opportunity is opened with an existing customer. Using the Yammer app for mobile and tablet devices, staff can keep track of CRM and other enterprise wide conversations within the context of a social news feed.
Licensing changes – New licensing models offer more granular flexibility for how organisations license the staff who use CRM. Rather than having to purchase the same license for all users, organisations can now also purchase a lower cost license with reduced functionality to suit their staffing needs.
Inline editing of grids – Productivity will be improved by the ability to quickly and easily edit and update product information for opportunities, quotes, orders and invoices directly into the grid layout.
Click-to-call functionality – Lync or Skype click-to-call integration means staff can call customers directly from CRM. A phone call activity will automatically pop-up so that you can record the details of the call without having to click anywhere else in CRM. This will help with staff productivity and ensuring key information is being recorded in your CRM.
Access Teams – Businesses can quickly share and collaborate on CRM information outside of the standard security model using pre-defined Access Teams. For example, you can share an Opportunity record if the required products or services span multiple business units within your organisation. This ensures your security model is robust yet flexible at the same time.
Workflow Actions – Standard workflow actions can be combined to create powerful functionality for use in different areas of the application. For example, submission of an opportunity for approval can be created as a custom action using a combination of Update and Assign workflow actions. This custom action can then be called from another workflow, from the command bar via a Web Resource or externally via a web service call. This enables CRM to be integrated with other line-of-business applications more efficiently than before.
Staged upgrade path from CRM 2011 – For organisations moving from CRM 2011 to CRM 2013, there are a number of different upgrade paths to suit different change management and training requirements. Any supported customisations in CRM 2011 will have a supported upgrade path to CRM 2013.
Recently I found another interesting tool for CRM.
Common: General Methods used for various purpose.
Rest: Organization Data Service functions including CRUD, Associate, Disassociate, etc
Soap: Organization Service functions including CRUD, Fetch, Associate, Disassociate, etc
Extension: jQuery extension to utilize WebResource to extend CRM 2011 / CRM 2013 including dependent OptionSet, field tooltip, add custom filter view to lookup field. (Some Methods ‘Unsupported’)
Download link to codeplex – http://xrmservicetoolkit.codeplex.com/
How to use it in CRM –
1. Add a reference to the XrmServiceToolkit.js file on your CRM form
2. Add a reference to JQuery 1.7.1 or above on your CRM form
3. Add json reference on your CRM form
4. Thats all!
Refer to the documentation section on codeplex for usage samples.
To create a read only user in CRM –
1. Create a new Business Unit “Read Only” with root BU as the parent BU
2. Create a new Security role “Read Only” with only Read permissions on all the entities in the system.
3. Assign the Read Only role to “Read Only” team.
4. Change the BU of the Read Only user to “Read Only” BU.
Hope it helps.
Out of the box CRM doesn’t allow you to setup a custom tooltip. To add a custom tooltip in CRM.
replace crmfieldscehmaname with the actual schema name. (this is case sensitive)
2. Add following method
3. Add following method
4. Call the Addtooltip method method on load of the form. Pass the control id and the tooltip text.
Hope it helps.
OnLoad of Case form call following code –
Change the Guid of the view you want to use. Please note, the value of the Guid will change for every environment / organisation.