Microsoft updates and improves Dynamics 365 products very often (September 2020 updates).

The most visible and remarkable change is the implementation of a new Unified Interface. The new design has lots of advantages and is more adaptive to different devices and browsers. Also, it remains unchangeable for all Dynamics 365 products - Unified Interface enables easy and comprehensive navigation of all dynamics 365 products.

Similar user experience + Common Data Service = Good prerequisites to unite all Microsoft products and build one holistic ecosystem.

In this article, I will tell you how to overcome UCI problems. As a relatively recent Microsoft update, the interface has some issues for now. Users who have been working with the old Legacy interface for years need time to get used to a new interface. And, urgent work has no time for looking into the interface issues.

Perhaps you have faced the following:

issues with web resources, and obtaining data. Some scripts that used to work fine in the old interface got errors in the UCI;
some custom ribbon buttons may stop working because of the script issue mentioned before;
problems with displaying ribbons because of not generated metadata;
the subgrid of the form may contain records of the entity which is not available in the UCI (option Enable for Unified Client is “No” on this entity);
some entities can be read-only in the UCI;
some problems were reported about the lookup field (the record name is not displayed in it);
in the old interface, there was a very convenient opportunity to see the workflow sessions associated with the current record. Unfortunately, we do not have it in UCI;
no support for composite fields on forms. The most famous composite field is a Fullname on Contact entity (fullname = firstname + lastname). These fields are useful. And it is problematic if you use them in scripts because UCI will throw an error.