I am migrating from 8.2 On Premise to v9 Online.
I have run the Dynamics 365 V9 Javascript Validator in the XrmToolbox and can see a number of issues.
They are:
- Method Xrm.Page must be replace with ExecutionContext.getFormContext
- Method Xrm.Page.context must be replace with Xrm.Utility.getGlobalContext
- Method Xrm.Page.context.getUserId must be replace with globalContext.userSettings.userId
- Method Xrm.Page.context.getUserName must be replace with globalContext.userSettings.userName
- Method confirmDialog must be replace with Xrm.Navigation.openConfirmDialog
- Method alertDialog must be replace with Xrm.Navigation.openAlertDialog
- Method openEntityForm must be replace with Xrm.Navigation.openForm
- A SOAP messages is detected. This must be replace with Use a custom control
To me it looks like 1-7 all relate to the deprecation of Xrm.Page. Looking at the documentation it is not 100% clear that this is the case for all 7 and wanted to check with the forum that my plan to push the solutions into v9 will be fine and that we can update all these issues post migration without anything breaking?
There are numerous instances of no 8 on our solution. The English in the tool is not great. My expectation would be that these SOAP elements will work also but that there is likely a newer technique that would be recommended. Again can I deal with these in the future, post migration?
*This post is locked for comments
I have the same question (0)
