How To Disable Unified Interface in Dynamics 365

All current version Microsoft Dynamics 365 trials and environments are defaulted to the “Unified Interface Only” setting. This is a good thing since Microsoft Dynamics 365 Unified Interface is here to stay and the previous “Legacy Web Client” interface is deprecated as of September 2019.

For certain situations where we need to run “Legacy Web Client” such as for testing existing setups – how do we enable our “Legacy Web Client” interface?

Firstly – the setting “Use Unified Interface only” is no longer listed under the Dynamics 365 Client’s Advanced Settings >> Administration >> System Settings >> General area

So where did it go?

The “Use Unified Interface only” setting is now found in the Power Platform Admin center!

Here are the steps to navigate to this setting:

Open Power Platform Admin center >> click Environments >> select the Dynamics 365 environment >> click the Settings button >> click the Behavior setting >> disable or enable the “Use Unified Interface only” setting

Ref: https://mscrmonline.wordpress.com/2019/11/11/how-to-disable-unified-interface-only-setting-in-dynamics-365/

Comments

Microsoft Dynamics 365 CRM Troubleshooting Solution Import Errors

Remember when CRM life was so much simpler that solutions did not yet exist? If you had separate development and production environments and you wanted to move your customizations, you simply clicked Export Customizations and voila! It was done. Those were the days. Nostalgia Warning – in case you’ve forgotten, here’s a screenshot to jog your memory: With CRM 2011, the concept of solutions was introduced, giving us a new set of powers – by picking individual entities, workflows, etc., we now had the ability to group together and move only those customizations we wanted to include in our solution. The next great solutions advancement came with CRM 2016: we can now select specific components within each individual entity – so instead of moving the entire contact entity, for example, we have the option of moving only a certain view or field within the entity. And we can do this without having to hack the xml in the zip file. (By the way, if you want to learn more abou...

How to Filter SubGrid Lookup view in Dynamics 365 CRM

How to Filter SubGrid Lookup view in Dynamics 365 CRM. Please check the comments in the below code and do follow the steps accordingly and call the filterSubGrid() funtion on onload. var LastQuery = ""; function filterSubGrid() { debugger; setSubgridLookupFiltering(); } function AddLookupFilter(entity_type, customFilter) { var subgridLookup = Xrm.Page.getControl("lookup_Contacts_Participants"); subgridLookup.addCustomFilter(customFilter, entity_type); } function setSubgridLookupFiltering() { var subgridAddButtonId = "Contacts_Participants_addImageButton"; //Try to get the element from both the current and the parent document. var subgridAddButton = document.getElementById(subgridAddButtonId) || window.parent.document.getElementById(subgridAddButtonId); //This script may run before the subgrid has been fully loaded on the form. If this is the case, //delay and retry until the subgrid has been loaded. if (subg...

How to prevent record from saving in Dynamics CRM using Javascript

From time to time you might need to add some validation to the save event of an entity, this actually used to be an approach I would use on a regular basis but since the introduction of business rules have found myself doing this less and less. But still, knowing the ability is available is handy. When you define the onsave event function, you must tick the “Pass execution contact as first parameter” option. (See below) Having done that you can create an onSave function with code similar to the example I have shown below. Note forgetting the “(context)”, which will take the context parameter allowing you to prevent the save when needed. function onSave(context) { var saveEvent = context.getEventArgs(); if (Xrm.Page.getAttribute("telephone1").getValue() == null) { // *** Note: I am using an alert for testing a notification maybe better! alert("Put in a phone number!"); saveEvent.preventDefault(); } } Note: This simple example might be better achi...

Dynamics 365 CRM

Search This Blog