You’re offline. This is a read only version of the page.
2,051
We are currently developing for one of our clients in classic interface. A lot of development has been done so far with classic interface and some of tasks are still under development.
There are lot of functionalities, which use Xrm.Page directive too.
Now, our dilemma is, should we move the client to Unified Interface at this stage and validate all the developed features again at new UI.
OR
Should we continue with the classic one, do the GO LIVE for the client at the end of this year.
Could anybody advise on this? Any help would be much appreciated.
*This post is locked for comments
The UCI is a big change and will break functionality that used to work in classic such as Xrm.Page and DOM level changes, as you say.
Without having full knowlege of the scope of the work I can't offer you answer on this but what I would recommend is to read the official Microsoft paper on the Unified Interface Playbook http://download.microsoft.com/download/A/F/3/AF3D45A7-4F38-41BE-8956-1DF7A4A5AFDB/dynamics365unifiedinterfaceplaybook.pdf
I would recommend taking into account the scale of the change (how much work to remove relience on Xrm.Page and DOM code?), the most important task is to ensure nothing breaks on go live. If you have time do move to UCI with sufficient testing in place then do, as the classic interface will eventually be deprecated and not work - although Microsoft tend to leave lots of time for migration for big features such as these.
I'm working on a very large project and have adopted the hybrid strategy by creating distinct apps for certain job roles and leaving some of other underused and less businsess critical functionality in the old classic interface due to not having sufficient time to test and deploy. This will get migrated once we have sufficient resource to complete and test this.
For users it can be quite a paradigm shift, but can be turned around into a positive once they see and understand the benefits the UCI interface brings and its in use.
Hi,
Although MS has deprecated the old Xrm.Page, and the recommendation has been to move to UCI, Microsoft has not yet officially deprecated the classic interface, which will give you 6 to 12 months until you will have to do this officially, but I believe that will be coming sometime soon.
If you have the time, I would recommend moving to UCI. It will not take as long, and it is something that you will have to do anyway soon.
Good luck.
For me if your customer are allowing and giving time to move to unified interface , my opinion is to change your code according to unified interface. You may know classic API will be deprecated in slowly so it would be great if you provide customer with latest UI supported at the same time of Go-Live.
Replacing Xrm.Page would not take much time , think like you will get the advantages of the formContext over Xrm.Page.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
54
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
