Microsoft Dynamics CRM product team just announced the deprecation of some older Dynamics CRM components in their blog article: https://blogs.msdn.microsoft.com/crm/2016/06/17/deprecation-announcements-with-dynamics-crm-online-2016-update-1-and-microsoft-dynamics-crm-2016-service-pack-1/.

dynamics crm components deprecation

 

Now, what does it mean? What actions that we need to do?

Let’s begin with the highlighted components that are marked to be deprecated.

  1. Deprecation of the Microsoft Dynamics CRM 2011 endpoint

Dynamics CRM 2011 endpoint has been around and used by multiple CRM versions 2011-2016 (v5.0-8.0). Developers might have been accustomed to this endpoint for now, however with the Microsoft’s direction of providing a modern API for Dynamics CRM, this Web API endpoint will be the way to go.

Some of the impacts of this update:

  • Any usage of the older oData endpoint should be updated using the new Web API. This would be around your javascript/web resources. This would be the best time for organisations to start analysing, planning and updating the code to point to the new API.

Note: Web Service connectivity through CRM SDK will be covered in the next item.

  1. Updates to the CRM SDK assemblies

Microsoft Dynamics CRM product team is updating their SDK assemblies to utilise the new Web API endpoint (https://msdn.microsoft.com/library/dn281891.aspx#bkmk_assemblyUpdates). The impact of this update is: updating the CRM SDK reference to use the latest version (v. 8.1.0 or later) to make sure the current application can function properly. Regression testing and end-to-end testing might be required for your organisation to ensure smooth transition of this update process.

  1. Removal of the Use legacy form rendering option

Dynamics CRM 2015 Update 1 introduced a new form rendering engine that is more efficient in performance. This feature became optional to support transition from the legacy form rendering to make sure it won’t create any blocker to the process in the business. Now with this deprecation announcement, organisations should take time to embrace this new update. Perform any regression and end-to-end testing of any of the script to ensure that this new form rendering will work well within your solution.

Note: Some of the new JavaScript functions such as Auto-Complete is also only available in this new form rendering engine. So, it’s a good thing to start embracing this update.

  1. Deprecation of some knowledge management entities

If you are using the knowledge management capability from the previous version of Dynamics CRM, this deprecation means a migration for your organisation to move the records from the old entities (KbArticle, KbArticleComment, and KbArticleTemplate) to the new entities (KnowledgeArticle and KnowledgeArticleViews entities to work with the knowledge articles in CRM, and use the KnowledgeBaseRecord entity when using Parature as the knowledge source).

  1. Removal of support for older Android versions

Microsoft is planning to remove support for Android 4.2 and 4.3. Newer release of Microsoft Dynamics CRM app for Android will need newer version of Android. If your organisation is using Android tablet/mobile app for Dynamics CRM, it is advisable to update to the latest version.

  1. Reminder that the Microsoft Dynamics CRM List component is deprecated

Dynamics CRM 2015 Update 1 introduced the Server-based SharePoint integration. If you have used the SharePoint list component for SharePoint integration, it is advised to look into the Server-based SharePoint integration. Luckily, Microsoft now has supported the hybrid scenarios for the possible deployment models of both CRM and SharePoint.

More information: https://technet.microsoft.com/en-gb/library/dn531154.aspx.