"This app is designed for the legacy web client and might have features or customizations that aren’t supported in Unified Interface. For best results, update it to Unified Interface." after switching to Unified Interface

(0) Share

Report

Posted on by HelloClay

Hi there,

We just switch over to the new Unified Interface. We booked it with Microsoft and they did the UI transition for us. Everything seems to be working as it should. However I can see "This app is designed for the legacy web client and might have features or customizations that aren’t supported in Unified Interface. For best results, update it to Unified Interface." in the banner. Is this something I need to be worried about?

Many thanks

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Henry J. 5,237 on at

Like (1)

Report
Copy link

Link copied!
Hello,

First, congratulations on your successful switch to the Unified Interface and glad everything works fine for you!

You're seeing this message because you are still using the legacy "Dynamics 365 – custom" app and not an actual model-driven app.
This article explains this in details: https://docs.microsoft.com/en-us/power-platform/admin/enable-unified-interface-only#dynamics-365---custom

To fix this, what you need to do is to have your users use a model-driven app instead of the legacy "Dynamics 365 – custom" app.
There are two distinct ways to easily achieve this:

Use Dynamics 365 first-party apps, such as "Sales Hub" (this will contain entities such as leads, opportunities, quotes, etc.) or "Customer Service Hub" (this will contain Cases, Knowledge Base Articles, Queues etc.)

Create your own model-driven app, where you can choose the entities, forms, views etc. that you want to display in your app sitemap.
The quickest to do this based on your current sitemap is explained here: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/transition-web-app-existing#create-a-new-model-driven-app-in-the-new-solution

In both cases you should make sure that your users, thanks to their security roles, can properly access these apps.
You will find guidance on this here:
https://community.dynamics.com/365/unified-interface/b/unified-interface-team-blog/posts/quick-tip-how-to-set-up-the-required-user-permissions-to-access-unified-interface-apps

Chapter 3: Transition of the Unified Interface playbooks should provide sufficient guidance to define the best app strategy for your business:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/unified-interface-playbook

When you are done, you should also disable the "Dynamics 365 – custom" app for non-admins to streamline their user experience.

Henry

Was this reply helpful? Yes No
HelloClay 30 on at

Like (0)

Report
Copy link

Link copied!

Hi Henry, Thank you. Would it be a problem if I continue to use Legacy "Dynamics 365-custom" app? Could I just ignore the message?

Was this reply helpful? Yes No
Verified answer

Henry J. 5,237 on at

Like (0)

Report
Copy link

Link copied!

Hello,

This will become an issue at some point but we don't have a deadline for its removal yet.

The legacy web client app should only be used temporarily for backwards compatibility with custom and third-party legacy functionality that you have not migrated to Unified Interface.
It is not designed for Unified Interface and can cause unexpected errors and experience.
For the best user experience, port all custom and third-party functionality to model-driven apps for Unified Interface.

The fastest way to do this would be to follow these steps:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/transition-web-app-existing

Henry

Was this reply helpful? Yes No
HelloClay 30 on at

Like (0)

Report
Copy link

Link copied!

Thank you :)

Was this reply helpful? Yes No