Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Unified Interface Transitioning from Classic Interface

  • 1.  Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Mar 20, 2019 01:29 PM
    Hello All,

    Was looking for any insight on any other businesses who used to use the older "Classic Interface" (not sure what it's actually called) versus using the newly introduced Unified Interface (UI). As I understand it, and I may be mistaken, but during the last CRM Group I attended did mention that eventually, potentially even at the end of this 2019 year, Microsoft would be moving towards using only the UI setup instead of the Classic Interface. This was said to be the move, much like moving from process/workflows within Dynamics, and instead replacing it with Microsoft Flow. Virtually working the same, but better. My questions are;

    1.) How hard is it to duplicate your currently used environment's interface and create it within the new Unified Interface?

    2.) Are there any processes/chains that are currently slaved to the old Classic Interface, that are no longer necessary within the Unified Interface?

    3.) If you have switched to the Unified Interface already, what would be some best common practices to take note of, or common pitfalls to avoid?

    I appreciate any help,
    Thank you,

    ------------------------------
    Nicholas Arbour
    TEKLYNX
    Whitefish Bay WI
    ------------------------------
    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 2.  RE: Unified Interface Transitioning from Classic Interface

    MICROSOFT MVP
    Posted Mar 20, 2019 06:23 PM
    @Nicholas Arbour - Hopefully, this information will provide some helpful insights.

    1) There are a few differences between the behavior of the "classic UI" and the new Unified Interface. However, the basic form layout will carry over. I have noticed, for example, that the "Address 1" (concatenated field) does not render in the Unified Interface. You will need to put the individual Address fields on the form.

    Also, you need to consider any custom buttons on the Command Bar that you may have in the "classic UI". If you used the "Ribbon Workbench" to create these, there are a few modifications you need to make so that the buttons render and work correctly.​

    The other consideration is that the new Unified Interface utilizes model-driven apps to "render" the interface. This will allow you to control the menu items in the navigation. You have greater control over what is displayed versus what is not.

    You can create your own custom mode-driven apps instead of using the OOB options of "Sales Hub", "Customer Service Hub", etc. I wrote an article on this a while back, but you will need to choose "Unified Interface" when setting of the app type. Actually, this is only option you can choose now.

    2) The "Settings" area is still rendered in the "classic UI".

    3) Be sure you plan on how you want to deploy the model-driven apps to your various departments or teams. Understand that the Unified Interface is what is used in the Dynamics 365 for Phones/Tablets.

    Review the Known Issues of Dynamics 365 to see if there are any impacts to any areas you currently use or plan to use.

    ------------------------------
    Aaron Back, MCSE
    Sr. Microsoft Dynamics 365 Consultant
    www.acemicrotech.com
    _______________________________________
    CRMUG Board Member
    CRMUG Chapter Leader - Cincinnati, Ohio
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 3.  RE: Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Mar 21, 2019 11:01 AM
    Hello Aaron,

    Thanks for the feedback, I'll take this under consideration. But for clarification, when you say this is used for the mobile experience, is that the ONLY thing it's used for? Is there no reason to update our 'classic UI' to the new UI because we use computers and not mobile devices to do business? Or can they be used for both, but the intention was to use them on mobile devices? I appreciate the links, I'll look into these before we decide to move over to the new UI, if we still wish to after my findings. Again, I appreciate the help/feedback.

    Thank you,

    ------------------------------
    Nicholas Arbour
    TEKLYNX
    Whitefish Bay WI
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 4.  RE: Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Mar 22, 2019 10:02 AM
    Hi Nicholas,

    Upgrade Notes
    I wrote up some of the notes that we took when we upgraded.

    We have been creating a 'Model Driven App' for each of our different groups that use CRM.
    Currently we've built 6 of them with plans to build at least 2 more.  They are relatively easy to put together as you just need to design the site map and remove entities, forms, views, dashboards, etc. that you don't want to see in your CRM.

    Biggest pitfall so far for us
    The biggest issue post deployment that we've run into in UCI system has been trying to automate urls.  This gets even more complicated because each app needs it's guid in the URL.  So let's say there is a single record that Sales Reps and Financial Service Reps both need to see a record and you want to notify them in an workflow email.  The current workflow 'Record (URL)' will take them to the legacy interface.  If you build your own URLs you will need to send the Sales Reps to their Model Drive App and financial services to their Model Drive App.

    Where the issue of URLs gets even more scary is if you have heavily customized your dynamics environment with hard coded links in javascript.  If done incorrectly, a user in the new UCI will click a link (let's say to create a prepopulated record) and the new form will open in the legacy interface.  This issue however won't be a problem if the javascript is using the xrm's openEntity() function which does work well in the new UCI.

    Our biggest user group of CRM is our Customer Service Representatives which rely on Powerobject's Power Phone, a tool to help an incoming call open a record in CRM.  Power Object's is still working on compatibility with the new UCI.  When an incoming call comes in and a user selects an existing record it pops them back out to the legacy interface!  We've reported this to them and they should have a fix coming soon.  I tell this story though because it's not just your own javascript you may need to look at, but your ISV's.

    Overall I really like the UCI.   While you don't use mobile, if you ever did there is very little you need to do to make it compatible with the UCI.

    ------------------------------
    Travis Judd
    CRM Developer
    Trek Bicycle Corporation
    WATERLOO WI
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 5.  RE: Unified Interface Transitioning from Classic Interface

    TOP CONTRIBUTOR
    Posted Mar 25, 2019 07:43 AM
    @Nicholas Arbour, good questions! I'll try to answer from our perspective.

    We are currently split with some users still on the classic interface and others in the unified interface. We have launched Dynamics for some new user groups recently and the functionality that meets their needs is present in the unified interface. There was no need for them to use the old and then have to learn the new.

    We have a couple groups who we have switched over. Again, the functionality they use is working well in the unified interface. Their transition was very smooth.

    Then we have our users who are rely on functionality that is currently not working to our satisfaction in the unified interface, so they are still in the classic. One thing that had been missing in unified interface that is coming with April's release is Audit History. Our users do a lot of filtering within views and that was also pretty clunky. Our testing in the April release shows much improvement there, too. The roadblocks are slowing being removed, but some are still present.​ We have an ISV that just gave us their updated solution. I haven't had a chance to test it yet, but if it works, we're much closer to being able to switch people over (whenever I have the time to build the apps!)

    The way we've been determining whether we can move a user group over is just to set up a test app and work in it. Also, paying attention to these chats and other resources online has helped, too.

    It did take us some work to prepare for the users to use the unified interface. Each of our user groups has a different layout on the account form to meet their team's needs. Due to the tabbed nature of the unified interface forms, our form layouts were/are not friendly in the unified interface. We've taken the time to create a new layout to take advantage of the tabs. Other than creating new forms and building out the sitemaps, it's really been pretty easy.

    My suggestions for some smallish things to watch out for are
    • form layouts - are they tab friendly?
    • filtering on views

    Testing things out will help you tremendously. There are many benefits to the unified interface, but it is different and not everything works there yet.

    Best of luck!

    ------------------------------
    Julie Reynolds
    Enterprise Information Steward II
    Brotherhood Mutual Insurance
    Fort Wayne IN
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 6.  RE: Unified Interface Transitioning from Classic Interface

    MICROSOFT MVP
    Posted Mar 25, 2019 11:13 AM
    @Nicholas Arbour - No, the new UI is NOT just for the mobile experience. It is used in the browser on the computer. I mention the mobile experience because a user may have the mobile app on their phone or tablet, and also use the computer. If you have not transitioned to the new UI, then the user will have an inconsistent experience. The phone/tablet currently use the new UI already. So, the user will have one UI experience on their phone/tablet and a different one on their computer.

    ------------------------------
    Aaron Back, MCSE
    Sr. Microsoft Dynamics 365 Consultant
    www.acemicrotech.com
    _______________________________________
    CRMUG Board Member
    CRMUG Chapter Leader - Cincinnati, Ohio
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 7.  RE: Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Mar 26, 2019 01:35 PM
    Hello All,

    Thank you all for your advice and information. Glad to know this isn't only for the mobile experience or was mainly geared towards it. I appreciate the heads up on the common issues occurring within the environment due to the change, that will have to be something I look out for. I concur with the DEV testing regarding the tab-friendly Forms, as I have seen similar issues when regarding quick changes to tabbed information and filtered views. I was recently informed, as well as within this thread, regarding the updates coming in April. This should be of great help in updating the functionality of the new UI, including adding some features on the Main Ribbon for running workflows, reports, and audit history as on demand processes. Or at least that is what the information I received stating the upcoming patch notes. I will definitely need to start building this in my DEV environment for some troubleshooting and planning. I thank you all again for your help, looks like I have some building/testing to do.

    Thank you,

    ------------------------------
    Nicholas Arbour
    TEKLYNX
    Whitefish Bay WI
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 8.  RE: Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Dec 04, 2019 11:19 AM
    Edited by Shawn Hickey Dec 04, 2019 11:22 AM
    We have been operating out of the classic interface and are encouraging users to move to the new Unified Interface.  In our Development environment we decided to set the Unified Interface as the default to evenually force all users to use it and noticed a few problems
    1. The URL we have been using for the classic interface now takes you to a list of all apps you have access to, instead of immediately launching your default app.  It appears there is no "default app" in the Unified Interface.  This will cause a lot of confusion to our 2,600+ users who have personally bookmared the legacy URL in their browsers
    2. Clicking on dynamic links from workflow notifications now open the record in the new Unified experience (yay!), BUT the site map isn't available so it isn't possible for the user to navigate to a different record or entity from the record they are looking at
    3. Navigating to our previous classic app doesn't launch it in the classic interface, so there is no way to get back

    Has anybody else experienced these issues or others?  We were hoping to force our users to the new unified interface in January but I'm not sure how we can without causing confusion to our end users!

    ------------------------------
    Shawn Hickey
    Burns & McDonnell
    Kansas City MO
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 9.  RE: Unified Interface Transitioning from Classic Interface

    Posted Dec 05, 2019 08:50 AM
    Hi Shawn,

    Under Manage Roles of the app, you can add in an App URL Suffix which will give you a new link to that app. When users use this link instead of the links you currently use it will take them straight into the app and UCI and will bypass this list of apps. I suggest you change any bookmarks and shortcuts to this new app.

    I believe it you use this new app link within the workflow emails it will then open up in classic interface. There is a post here that describes this: butenko.pro/.../howto-send-record-url-pointing-to-specific-model-driven-apps



    ------------------------------
    Nicole Williams
    Technical Architect
    Concurrency, Inc
    Brookfield WI
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 10.  RE: Unified Interface Transitioning from Classic Interface

    D365UG/CRMUG ALL STAR
    Posted Dec 05, 2019 09:05 AM
    Hey Shawn,
    I can speak to the first issue.  We also had that issue and the only way I could resolve it was to remove access (security roles) to those other apps.  I saw that someone suggested a new URL, but we were in the same boat as you.  Many had the URL bookmarked in their web browser.  We updated the URLs on our internet sites, but obviously could not control what others had bookmarked.  To us more technical people, it seems like a simple request to ask CRM users to edit their bookmark, but it is not a priority and not that easy for the engineering type folks :)

    ------------------------------
    Laura Mortick
    Marketing Information Systems Manager
    Terracon
    Olathe KS
    Kansas City CRMUG Chapter Leader
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


  • 11.  RE: Unified Interface Transitioning from Classic Interface

    GOLD CONTRIBUTOR
    Posted Dec 05, 2019 09:22 AM

    Hi Shawn!

    https://admin.powerplatform.microsoft.com/


    Select your environment and go to settings

    Select Product Behavior

    Then turn on

    This should convert your legacy site map into a default UI.

    The legacy URL will still tke them to the App selection screen, with the URL redirecting to crm.dynamics.com/main.aspx?forceUCI=1

    On the app selection screen you should see your default app which should be converted once you click on it.  When you click on it it takes you to .crm.dynamics.com/main.aspx?app=d365default which should have the look and feel of the new UI with your legacy sitemap.

    I'm not sure if I have a solution, but I guess you could you work with your networking team to redirect your internal users from crm.dynamics.com to  .crm.dynamics.com/main.aspx?app=d365default which should bypass the app selection page?  The networking team may have a better solution.

    Just an FYI on what we have done at my company.  Over the last year we've transitioned each of the different teams into their own model-driven apps and given them links to the apps along with directions to update their bookmarks.  Eventually, we want to turn off the default environment entirely.  I think ideally it would be great if they only had access to one app that they would just redirect into it.

    Hope this helps or gives you more insight.

    Thanks!







    ------------------------------
    Travis Judd
    Business Apps Specialist
    Trek Bicycle Corporation
    WATERLOO WI
    ------------------------------

    The first step toward cloud success. - Migrate from CRM to D365 with expert guidance from Microsoft. I'm Ready


If you've found this thread useful, dive deeper into User Group community content by role