Important changes coming in future releases of Microsoft Dynamics CRM
Applies To: Dynamics CRM 2016, Dynamics CRM Online
Developers can use this information when they plan software development for future versions of Microsoft Dynamics CRM. With the Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 releases, the following features are deprecated: CRM 2011 endpoint, some knowledge management entities. There are also details about removal of the legacy form rendering option and future updates to the SDK assemblies. For information about changes that administrators and IT professionals should consider to prepare for future versions of CRM, see TechNet: Important changes coming in future releases of Microsoft Dynamics CRM.
Deprecation means that we intend to remove the feature or capability in a future "major" release of CRM. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work. We are notifying you now so that you have sufficient time to plan and update your code before the feature or capability is removed.
Beginning with the CRM 2016 (8.0) release, a new OData 4 endpoint was added to the CRM application stack. This endpoint is known as the Web API. The Web API provides a development experience that can be used across a wide variety of programming languages, platforms, and devices. The Web API is intended to replace the CRM 2011 endpoint, also known as the SOAP endpoint, for accessing the CRM Organization web service and other provided web services.
As of the release of Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (8.1.0), the CRM 2011 endpoint has been deprecated. The 2011 endpoint will be removed sometime after CRM version 9. We plan to provide updates to the CRM SDK assemblies and tools over the next several minor releases, retargeting them to use the Web API instead of the 2011 endpoint.
We strongly encourage you (developers) to use the Web API for accessing the CRM web services when you write new application code. You must update existing applications to use the CRM Web API for accessing the CRM web services between now and the removal of the 2011 endpoint. When you develop plug-ins and custom workflow activities, continue to link those projects to the CRM SDK assemblies. The CRM SDK assemblies will be updated to use the Web API. This update will be fully transparent to you and any code written using the SDK itself will be supported.
Additional details will be published in future SDK releases. For more information about the Web API, Use the Microsoft Dynamics CRM Web API
Some entities used for knowledge management in CRM are deprecated: KbArticle, KbArticleComment, and KbArticleTemplate. You must use the newer KnowledgeArticle entity (introduced in CRM Online 2016 Update and CRM 2016) for knowledge management in CRM. More information: 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 TechNet: 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 Client-side programming reference, report this to Microsoft Dynamics CRM technical support.
Unsupported form objects or methods, remove these customizations or find a different way to achieve the results you want.
Due to changes in the underlying security architecture of CRM Online and its supporting systems, applications that currently use the CRM 2011 endpoint to authenticate against the CRM Online identity provider must be rebuilt with the most recent releases of the CRM SDK assemblies to prevent future service outages. For applications built with the CRM 2016 SDK, link those applications to the version 8.1.0 or later SDK assemblies. Planned updates to the Microsoft Dynamics CRM 2011 SDK, Microsoft Dynamics CRM 2013 SDK, and Microsoft Dynamics CRM 2015 SDK to address this issue will be announced through the CRM Team Blog. Applications that depend on any of the current assemblies will simply need to be re-linked to the updated assemblies to function normally.
This applies only to Microsoft Dynamics CRM Online.
Microsoft Dynamics CRM 2016 and CRM Online
© 2016 Microsoft. All rights reserved. Copyright