You’re offline. This is a read only version of the page.
We currently have many customized forms in CRM v8 - will they all need to be rewritten in Unified Interface to move to v9 if we want to use the new functionality? And is there any type of upgrade from the Classic Forms to UI? Also if we have say a classic form on Account, can we build a new UI form/app and switch to it then remove the Classic Form? I'm just not sure how this works. We will be building a new v9 environment, and our debate is whether or not to import our v8 organization in or to rebuild everything in v9 then import data.
Thanks.
Thank you Aric!
On top of your advice, Chapter 3 of the Unified Interface Playbook specifically focuses on the tasks of a transition project.
You can download the PowerPoint deck here: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/unified-interface-playbook
Hi Sam,
As you are moving from version 8, and again not sure what the complexity of your applications are, you just take a look at the features that have been deprecated in version 9 and determine what the best route for taking care of these are.
Some of the examples of the top of my head are JavaScript functions changes (use of formContext instead of Xrm namespace), deprecation of dialogs, and changing your JavaScript functions to use the OOB WebApi instead of the former REST API.
Hope this helps.
On top of the useful resources provided by Danielle, I would like to add that you don't need to upgrade or create new forms for Unified Interface.
Think of it more as a new rendering of existing customizations. So a same form can be used both on Web Client and on Unified Interface.
That being said, since the rendering is slightly different between Web Client and Unified Interface, it is a good opportunity to rework your forms so that they are optimized for Unified Interface. You can do so by doing a copy of the existing form and use it in one or all of your Unified Interface apps.
Hi Sam,
Think of the switch to Unified Interface as more of a transition. Depending on the current level of complexity of your environment, you may want to transition away from the web client in phases using targeted Model-Driven Apps for various business teams and/or use cases.
Your best course of action is to test the Unified Interface in a sandbox environment - ideally a recent copy of your production environment. Here you can create a parallel Model-Driven App in the Unified Interface, leaving your Web Client app as-is.
I recommend you review these two documents to help you get started:
Unified Interface Playbook: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/unified-interface-playbook
Quick Start Guide - add Unified Interface App to existing environment: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/transition-web-app-existing
We also have a published white paper on approaching the transition: http://download.microsoft.com/download/A/F/3/AF3D45A7-4F38-41BE-8956-1DF7A4A5AFDB/approaching-unified-interface-transition.pdf
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (