Important changes coming in future releases of Microsoft Dynamics CRM
Administrators and IT professionals can use this information to prepare for future releases of Microsoft Dynamics CRM. With the Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (on-premises) releases, some knowledge management entities are deprecated and older Android and iOS versions will no longer be supported. There are also details about removal of the legacy form rendering option and a reminder about the Microsoft Dynamics CRM List Component. For information about changes that developers should consider to prepare for future versions of CRM, see MSDN: Important changes coming in future releases of Microsoft Dynamics CRM.
In support of the latest technologies, these mobile device operating systems will no longer be supported in the Microsoft Dynamics CRM mobile app.
Android versions 4.2 and 4.3.
Apple iOS 7 and iOS 8.
More information: Support for CRM for phones and CRM for tablets
With Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (on-premises) release, the following entities used for knowledge management are deprecated: KbArticle, KbArticleComment, and KbArticleTemplate. These entities won't be supported in a future major release of CRM. You must use the newer KnowledgeArticle entity (introduced in CRM Online 2016 Update and CRM 2016) for knowledge management in CRM. More information: MSDN: Knowledge management entities
With Microsoft Dynamics CRM Online 2015 Update 1 we introduced a new form rendering engine (sometimes called "turbo forms" ) that provides improved performance. This new rendering engine became available for customers with on-premises deployments with Microsoft Dynamics CRM 2016.
Because such a change can introduce different behaviors in form scripts, we currently provide a Use legacy form rendering option in System Settings so that an organization can opt out if they detect problems. This is intended to be a temporary solution. As documented in What's new for administrators and customizers in Microsoft Dynamics CRM 2015 and CRM Online and MSDN: Write code for Microsoft Dynamics CRM forms, we recommend addressing issues as soon as possible.
The Use legacy form rendering option will be removed in the next major release. Legacy form rendering (sometimes called "refresh forms") is deprecated and will no longer be available. Only the rendering option will be removed; the form definition is still supported. Organizations who have not yet resolved issues with their customizations by using the new form rendering engine should take action immediately so that they will be able to upgrade to the next major version.
If you have turned on legacy form rendering, please turn it off and test your scripts. During testing, if you see breaking changes in forms that use:
The supported client API objects and methods documented in MSDN: Client-side programming reference, report this to CRM technical support.
Unsupported form objects or methods, remove these customizations or find a different way to achieve the results you want.
Although we first announced the deprecation with the release of Microsoft Dynamics CRM Online 2015 Update 1, as a reminder, customers currently using the Microsoft Dynamics CRM List Component for SharePoint Server are advised to upgrade to use server-based Microsoft SharePoint integration. For more information about how to configure server-based SharePoint integration, see Set up SharePoint integration with Microsoft Dynamics CRM.
Future releases of Microsoft Dynamics CRM applications and features, such as CRM for Outlook, export to Excel, and mail merge, will no longer be supported for use when you run them using Microsoft Office 2010, which includes Microsoft Office Outlook 2010. To prepare for this change, we strongly recommend that you upgrade to a later version of Microsoft Office. More information: Microsoft Office
The Microsoft Dynamics CRM Email Router will become deprecated in the next major release of Microsoft Dynamics CRM. To prepare for this change, we strongly recommend that you migrate all email routing functionality to use the server-side synchronization feature. More information: Migrate settings from the Email Router to server-side synchronization
© 2016 Microsoft. All rights reserved. Copyright