DYNAMICS 365 HOW TO SWITCH BETWEEN UNIFIED CLIENT INTERFACE (UCI) AND CLASSIC WEB INTERFACE

Due to many questions in the Dynamics community on how to switch between the new Unified Client Interface (UCI) and the Classic Web Interface, I decided to write this post to show you how to do it.

In the new V9 version, the default interface will be rendered in the Unified Client Interface; however, many users still prefer the original one and need to switch back to the classic web interface.

You have two options to switch between the new Unified Client Interface (UCI) and the Classic Web Interface

  1. From the advanced settings section
    • Click the Settings gear icon > Advanced Settings
      switch UCI to classic interface 1

    • Click Settings > Administration > System Settings
      switch UCI to classic interface 2

    • In the System Settings pop-up, scroll down and set No the option Use the new Unified Interface only (recommended)
      switch UCI to classic interface 3

    • You are now back to the classic web interface
      switch UCI to classic interface 4

  2. From the URL by adding a query string
    • If you check the URL rendered in the browser, you will see some parameters https://orgname.region.dynamics.com/main.aspx?forceUCI=1&pagetype=apps
    • In order to see the classic web interface, you can change the parameters as below https://orgname.region.dynamics.com/main.aspx?forceClassic=1
    • You are now back to the classic web interface
      switch UCI to classic interface 5

Bonus Tip:
Note that meanwhile, there is always the option to switch between the two interfaces and there are no news if the original classic web interface will be deprecated.
However, I recommend to get used to the Unified Interface because I believe it is the future and that Microsoft is investing in it and the classic interface will slowly fade away.


Hope This Helps!

Comments

Post a Comment

Popular posts from this blog

DYNAMICS 365 HOW TO HIDE RECENT RECORDS FOR LOOKUP FIELD IN UCI

Image
In UCI, a lot of behaviors have been changed comparing to the Classic Web Interface such as the tabs, BPF, and many others. Today, I will be talking about one of these behaviors which is the Recent Records in lookup fields. In a brief summary, the Recent Records feature will suggest the latest records that have been searched for, where the user can select one of them, and, the list of available records of the current view will then be displayed. This is a nice-to-have feature since it might help the users to speed up data entry. However, if the lookup has been filtered to display specific records, the Recent Records will not respect this filter and will keep showing records even is they should not. This scenario can lead to selecting a record by the user that is not allowed to be selected. Therefore, in this situation, it is better to hide the Recent Records t
Read more

SEARCH BY GUID IN DYNAMICS 365

Image
Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!! As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search. However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid. How it works, let's check the 3 different places where we can search for a records. Advanced Find search Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there. Quick view search Using the search box
Read more

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

Image
In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form. In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed. The following example will display a successful message if the save operation is completed, and a failure message if not. formContext.data.save(1).then( function () { alert("Successfully Saved!"); }, function () { alert("Failed while saving!"); });
Read more