Good afternoon, we have cutover from legacy web to UCI planned for sometime in late november 2020 for our prod environment. We have lots of previously created javascript (present and past developers) that has references to xrm.page. But a lot of it is in nested code blocks that are not being used anymore/obsolete.
So in our sandbox environment we have enabled UCI and running thru manual user tests to discover any behavioral issues with UCI. We are not changing any code unless some user testing reveals a script error in UCI. When that happens we analyze the error and usually it turns out to be xrm.page object graph related (ex. xrm.page.getAttribute()...). Then we analyze the relevant function call graph to ensure the getFormContext() based replacement gets passed in there. Then retest the script error thrown by runtime behavior. So far so good.
However we are not changing xrm.page references everywhere as it's in a lot of places in the script and in a lot of other scripts, and most of the references to xrm.page appear to be working as of Oct 2020 in the sandbox UCI.
However I do want to know when the actual removal of xrm.page object model from dynamics will take place. I understand as of oct 2020 it is deprecated but still operational. Is it reasonable assumption that we are still atleast 6 months away. If xrm.page based behavior is working and testing fine in UCI sandbox right now, will it continue to work in UCI prod on Dec 1, 2020 after we have cut over to UCI? And before the date in future when it actually won't work at all, how will we be notified that all xrm.page references needs to be converted over or javascript will break completely.
Basically I am trying to understand how much time we have to do a complete rewrite of these javascript libraries. Because what we are doing right now is surgical changes where we find issues during UCI testing.
Thanks
https://docs.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated
"Use of the Xrm.Page object as a static access to the primary form context is still supported to maintain backward compatibility with the existing scripts. Based on the feedback, we understand that the usage of Xrm.Page is high, and it won't be removed as soon as some other client API methods listed in this section."
