As a part of important changes coming in the future releases of Dynamics CRM, two major existing functionalities which had been in place from CRM 2015 version would be deprecated and find their details as below.
- Removal of legacy form rendering option
With Microsoft Dynamics CRM Online 2015 Update 1, 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, CRM 2016 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. We hope these kind of issues would be addressed soon.
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.
So Organizations be aware of this..
2.Microsoft Dynamics Email Router is deprecated
Discover more from ECELLORS CRM Blog
Subscribe to get the latest posts sent to your email.
ECELLORS CRM Blog 