Skip to main content

Getting the Most Out of Dynamics 365 Upgrades


Microsoft has settled into a schedule of providing significant enhancements to Dynamics 365 (formerly Dynamics CRM) every six months, so all of us who use the product must adapt to being in a constant state of adopting new features and preparing for the next upgrade.  Microsoft is investing heavily in development of Dynamics, and pouring the fruits of research and development such as artificial intelligence and analytics into the product.

The question for my clients is how to get the most out of this cycle of constant integration.  They want to know how much an upgrade will cost and how long it will take.  Here are some considerations that may help you make the best trade-offs for your organization.

I divide upgrades into three types of changes.   The easiest are improvements in performance or changes in the user interface that require no action on our part.  If forms or reports run faster, or Microsoft adds a new item to a toolbar, these improve the product without asking for a trade-off.  The only task it may require is for us to update user documentation or training materials when the screens change significantly enough to merit the update.

The second category is what I call negative changes -- when deprecation of an old feature causes our solution to break.  Microsoft has a pattern for this which involves early warning, so we usually have two or more versions which have backward compatibility before a feature is turned off or changed for good.  This post is a good example of Microsoft announcing feature deprecation, including the Outlook add-in, dialogs, mailmerge, Parature knowledgebase, and over two dozen APIs.  This kind of change is the reason that you must read the release notes as soon as they are published.  You have choices to make on when to replace deprecated features.  Sometimes Microsoft has announced the end of a product or feature only to extend it later, so bolder customers can wait until the last minute and hope for a reprieve, but I do not endorse this approach.

The most interesting category is improvements which allow you to enhance your solution, but that require action on your part. For instance, when Microsoft adds new apps such as Dynamics Project Service or Field Service, you may want to activate some of the features that they contain and have your users take advantage of these features.  In some cases they may replace customizations that you created before they were available, so you will need to migrate data and train end users.  Each version contains hundreds of new features, and offer many opportunities to take Dynamics to new heights.  Would you like to add artificial intelligence to analyze your client interactions? A chat bot to supplement live chat?

We recommend that you create a roadmap for your Dynamics solution and roll out new features over time rather than assume that your solution will remain static.  Users will come up with new requirements, new ways of accomplishing their work, and Microsoft will serve up new features that you will want to use.

Related Posts

5 Tips on Moving from Dynamics CRM On Premises to the Microsoft Dynamics 365 Cloud
Upgrading Dynamics CRM, Part 1
Upgrading Dynamics CRM, Part 2
Upgrading Dynamics CRM, Part 3

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