Transitioning Classic to new Unified Interface

(0) Share

Report

Posted on by Community Member

Hi everyone, so i've read the similar posts to mine. However what i'm mainly curious about is how the transition from Classic to new Unified would affect the entire system? For example would the new Unified interface affect Portals? And what are some known issues on the new unified interface and how should we prepare to go prevent these issues from happening?

Thank you

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Henry J. 5,237 on at

Like (0)

Report

Hello!

What it does change is how users render the application. Instead of the legacy web client to render the navigation, dashboards, views and forms with a legacy rendering engine, the Unified Interface essentially renders the same customizations in a more modern, performant and user-friendly way.

To tackle that transition, you generally adopt out-of-the-box apps that are on the Unified Interface (e.g. Sales Hub) or you create new ones.

If you don't upgrade your users to the Unified Interface through the use of new apps, because the "Unified Interface only" mode is be automatically turned on in October 2020 (you can enable it earlier if you are ready), it will force the rendering on Unified Interface.

That's why it's very important to test your apps before that day.

In order to prepare, I recommend you go through the chapter 3: Transition of the Unified Interface Playbooks https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/unified-interface-playbook

Henry

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Henry,

Awesome thank you for the reply, however I was also wondering what are some known issues in the unified interface that we should be aware of. For example I have read that ribbon buttons have been buggy with the unified interface and portal comments have also been buggy.

Was this reply helpful? Yes No
Suggested answer

Henry J. 5,237 on at

Like (0)

Report

There were a number of parity gaps in Unified Interface that have been addressed Release Wave after Release Wave.

I'm not aware of issues with Portals, but I would certainly advise that test your various customizations (e.g. custom buttons) to do an assessment of what would potentially need to be fixed.

If you have JavaScript, if would be good to run the Power Apps Solution Checker to identify deprecated methods or problematic patterns in your customizations: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-powerapps-checker

There are also features that don't work in Unified Interface, such as legacy dialog processes.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Would the Solution Checker also check for Portal custom javascript for example any custom javascript that was used inside an entity form or entity list?

Was this reply helpful? Yes No
Verified answer

Niktia Polyakov Mic... on at

Like (1)

Report
Hello!

Migrating to Unified Interface does not typically impact Dynamics 365 Portals or Power App Portals experiences.

Think of Portals as it's own player/renderer of select parts of the metadata on Forms and Views. General Portals is a sub-set of functionality found in Model-Drive Apps or Dynamics 365 Apps.

Here are couple more examples:

Typically you would have dedicated Views and Forms with layouts special to your needs for Portals that are then used on Entity Views or Entity Forms.

Also since we do not have XRM API on Portals UI you would not have same JS or HTML Web Resource likely using those, which is also why you typically have dedicated Forms for Portals to use.

Portals does not read Ribbons or other customization that is generally not compatible and not surfaced on Portals. Portals has it's own rendering of Notes or Attachments and several other components.

Portals advanced UI coded-customization would be done in via JS stored on in Portal configuration away from Forms code and using JS/JQuery that is not part of your migration process for Unified Interface you would not need to touch those Portal customizations.

Portals configuration and customization themselves actually made in their own modern Model-Drive App for managing Portal it self that is already in Unified Interface. Look for "Dynamics 365 Portals" "Portal Management" apps in your list of Apps. (If you do not see that please Update your Portal Solutions in our older Dynamics 365 Admin Center or contact Support for help)

Hope this helps!

BONUS: You can use Portal Checker to check for Portal specific issues, if this spots issues, again those those would not at all be related to your tasks for migration to Unified Interface and should be addressed on their own timeline. Portal Checker Docs: https://docs.microsoft.com/en-us/powerapps/maker/portals/faq#portal-checker

Was this reply helpful? Yes No
Henry J. 5,237 on at

Like (0)

Report

Thank you Nikita!

Was this reply helpful? Yes No
NeilLombard 46 on at

Like (0)

Report

Hi Nikita,

I am having an issue with the portal after the new unified interface update. On a Web Form, in a Web Form Step, the section containing the "Additional Settings" / in the Form Definitions Tab containing the Validation Summary Header Text, Instructions and 'Record not found message' does not display the field, only the field label.

Do you have any ideas on how to get the focus on the field / getting the fields to display?

Was this reply helpful? Yes No