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:
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
Thank you guys. Those are some really useful resources for understanding the new model.
As far as I can tell the existing code will continue to work through the migration for the time being. That means my first step will be to migrate and I can expect our system to continue to function.
Then we can plan out updating the deprecated code.
Hi
You could refer to Aric's posts, I found them very useful
community.dynamics.com/.../migrating-your-client-api-to-dynamics-365-ce-v9-part-i
community.dynamics.com/.../migrating-your-client-api-to-dynamics-365-ce-v9-part-ii-attributes
community.dynamics.com/.../migrating-your-client-api-to-dynamics-365-ce-v9-part-iii-controls
Go to below link and read each topic. It will give you better idea:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156