How to change Dynamics 365 CRM web interface from UCI to Classic version?

Recently created a Dynamics 365 CRM 30 days trial version (Ref: How to Setup Dynamics 365 30 days Online Trial version?) and it was navigating to CRM home page showing the list of UCI Apps, instead of showing CRM Classic Web UI.

Below is the screenshot for reference.


Later found that, the rendered URL was showing differently in the browser and having forceUCI and pagetype parameters.

https://CRMOrgName.Region.dynamics.com/main.aspx?forceUCI=1&pagetype=apps

If you want to see the old Classic Version of CRM, just use the parameter forceClassic=1, instead of forceUCI=1 and remove the parameter pagetype=apps in the URL and final URL will be like the below,

https://CRMOrgName.Region.dynamics.com/main.aspx?forceClassic=1

Bookmark the URL and explore CRM 🙂

Advertisement

Why the plugins implement IPlugin interface and Workflows (custom) inherits the Code Activity abstract class

Dynamics 365 CE/Power Platform, PowerApps, Power Automate, Azure by Vishal Grade

Someone asked me this question which is frequently asked in interviews i.e. why plugins implemented iplugin i.e. an interface and custom workflow inherit codeactivity i.e. an abstract class?

The purpose of question is to know why codeactivty is an abstract class and not an interface like iplugin?

So to understand the answer we fist need to understand the difference b/w interface and an abstract class:

What is an Abstract Class?

An abstract class is a special kind of class that cannot be instantiated. So the question is why we need a class that cannot be instantiated? An abstract class is only to be sub-classed (inherited from). In other words, it only allows other classes to inherit from it but cannot be instantiated. The advantage is that it enforces certain hierarchies for all the subclasses. In simple words, it is a kind of contract that forces all the subclasses to carry…

View original post 300 more words