Skip to main content

Tracking Feature Deprecations in Microsoft Dynamics 365 Customer Engagement



Cloud solution providers such as Microsoft have stepped up the pace of innovation, and are releasing features continuously rather than their traditional pattern of major releases every year or two.  This fast innovation means that users see new features and enhancements often, and you must account for how to train them to take advantage of them.

It also means that some old features are eliminated or replaced - this is called deprecation.  Microsoft publishes deprecation plans to alert administrators and developers so they can make timely changes to their solutions before a new version makes a feature break.

The typical pattern is to announce a feature deprecation more than one version in advance, sometimes supporting the old feature and the new feature, then issuing an update which eliminates the old feature.

Deprecation affects many aspects of Dynamics 365:

  • Apps or plug-ins may be deprecated, such as the Outlook Add-in for Dynamics which was replaced with the Outlook Dynamics App, or removing mobile apps such as the Microsoft Dynamics 365 for Blackberry App from app stores.
  • User interfaces including forms and menus are upgraded.  We are now in the transition to the Unified Interface from the legacy web client.
  • Developer changes such as the software development kit (SDK) or integration end points.  
  • Infrastructure changes such as email routers. 
  • Workflow automation techniques such as business process flows and replacing task flows with the new Form designer
Deprecation of developer features can mean that your Dynamics solution may stop working without refactoring your code to use the new features.  This may be minimized by striving for low code solutions, but even low code or no code solutions have required re-work in the past based on new versions of Dynamics. 

One of the prices for cloud innovation is vigilance for new changes, and only staying on top of the latest version of your products allows you to get the most productivity you can from them. 


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