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
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?
Thank you Nikita!
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:
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
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?
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.
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.
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
André Arnaud de Cal...
291,969
Super User 2025 Season 1
Martin Dráb
230,842
Most Valuable Professional
nmaenpaa
101,156