Upgrading code is a critical activity for an upgrade, especially if you are upgrading from an earlier version such as Dynamics CRM 2011. There are some client-side methods that are deprecated to make it easy to move from one client to another. So, even if you are upgrading from Dynamics CRM 2016, you need to upgrade your client-side code to make it compatible with Dynamics 365 CE. Although old methods can work due to compatibility support, they will stop working in some major Dynamics 365 CE releases. Let's discuss high-level changes that we need to make in our Dynamics CRM 2016 code, as follows:
- Xrm.Page: In Dynamics CRM 2016, the Xrm.Page object was used to refer to entity forms and fields from JavaScript written on entity forms as well as HTML web resources. But now, using Xrm.Page to access entity forms and fields in the script written for entity forms...