Skip to main content

Upgrading Dynamics CRM, Part 1

This is adapted from the InfoStrat White Paper "Upgrading Dynamics CRM." Download the full whitepaper here: http://www.infostrat.com/#!upgrading-dynamics-crm/c15ht

Microsoft offers major upgrades to Dynamics CRM every two years and minor upgrades every six months or more often.  In order to benefit from the latest features and functionality of these new versions, you must upgrade your CRM implementation from time to time.  For Microsoft Dynamics CRM Online users, your system will automatically be upgraded as new versions become available.  Microsoft also ceases to provide mainstream support for older versions, typically two releases prior to the current release.
 
In each instance of a major Microsoft Dynamics CRM release, new features have been added that may require you to change your solution if you want to take advantage of them.  For instance, Business Process Flows were first introduced in Dynamics CRM 2013. To effectively use this new automation feature, you would need to analyze how you would like to map your business process flows to CRM Business Process Flows and design an effective user interface on the appropriate forms. 
 
In major upgrades, custom code which worked in earlier versions but will no longer be supported in future releases may be “deprecated”, meaning that it will not work in a future release.  You do not have to make any changes when these warnings appear in a release, but it does suggest that you keep them in mind when planning other changes or updates.
 
As a Microsoft Dynamics CRM customer, it is important to understand the new features and functionality and determine the best timing and approach to bring your application to the latest version.

A Brief History of Microsoft Dynamics CRM


Microsoft introduced its CRM product in 2003. A minor upgrade version 1.2 was released soon after. Two years later, version 3.0 was released in December of 2005, skipping version 2.0.   Version 4.0 appeared in December 2007, and the first cloud version of Microsoft CRM – Dynamics CRM Online -- was introduced several months later.  The next version of the product was Microsoft Dynamics CRM 2011 introduced in February 2011. For CRM 2013, Microsoft changed its upgrade approach to upgrading cloud versions first, then on premise versions. The on premise version of Dynamics CRM 2013 was released in November 2013.  The latest major version of the product -- Dynamics CRM 2015 -- was released in in the fourth quarter of 2014.

Version
On Premise
Cloud (Microsoft Dynamics CRM Online)
1.0
January 2003
N/A
3.0
December 2005
N/A
4.0
December 2007
March 2008
2011
February 2011
January 2011
2013
November 2013
October 2013
2015
December 2014
November 2014

As of this writing, it is estimated that Microsoft has 40,000 customers using Microsoft Dynamics CRM [1]



[1] http://www.capterra.com/customer-relationship-management-software/#infographic

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do