No time to read now? How about listening to the article? Try it out in the player below!
As previously announced, Microsoft released the Wave 2 for Microsoft Dynamics 365 and Power Platform with a lot of news. With them, we also know some resources may be deprecated. We get so excited with the new resources that we may ignore the resources we’re using, which will be deprecated in the new wave.
To help you, I’ll share some resources that will be deprecated. Let’s go!
Internet Explorer 11 support for Dynamics 365 and Microsoft Power Platform is deprecated
With 2022 release wave 2, Internet Explorer 11 will be blocked. Please switch to a modern browser.
Effective December 2020, Microsoft Internet Explorer 11 support for Microsoft Dynamics 365 and Microsoft Power Platform is deprecated, and Internet Explorer 11 won’t be supported after August 2021.
Support for Microsoft 365 Groups and Yammer in Dynamics 365 is deprecated
Effective February 2022, support for Microsoft 365 Groups (previously known as Office Groups) and Yammer in Dynamics 365 will be deprecated. This will impact customers who use Microsoft 365 Groups and/or Yammer for collaboration in Dynamics 365. We recommend that customers transition to Microsoft Teams for more advanced collaboration functionalities. For information about integrating Dynamics 365 with Teams, see Integrate customer engagement apps in Dynamics 365 with Microsoft Teams.
The Analyze section, in mobile offline profiles, is deprecated
Effective September 2021, the Analyze action and the Offline profile report used to configure mobile offline profiles are deprecated. The Analyze feature is being removed because of Cross-Site Scripts (XSS) vulnerabilities. The report is used to identify components that aren’t available when you’re working in offline mode. The capabilities will be reimagined as part of the ongoing enhancements of the mobile offline configuration experience. There’s no action required by you.
Low-density headers in model-driven apps won’t be supported
Makers have moved away from low-density headers, and usage is low. Low-density headers don’t promote a highly dense experience and require users to always use the flyout for all controls across view-port sizes from small to very-wide.
Any current form that is configured to be “low-density” is automatically updated to render in a high density with flyout mode in a model-driven app. Below is an example of the high-density header with flyout:
So now, you just need to be sure you update any of your forms from a low-density format to a high density with flyout mode using the modern form designer. More information: Configure header density.
If you don’t make this change, the form no longer honors this setting at runtime. It also defaults to high density with flyout.
Form footers in model-driven apps won’t be supported
With the release wave 2, form footers won’t be supported in a model-driven app form. Microsoft brings us the main points to deprecate this feature:
- The footer doesn’t meet the Microsoft Web Content Accessibility Guidelines (WCAG) 2.0 compliance for accessibility.
- Data density is highly impacted by the form footer and doesn’t support a good customer experience. Controls aren’t discoverable and lead to many customer usability issues.
- Makers have moved away from adding controls into the footer and there’s low usage of other controls, out of box or custom, in the current form footer experiences.
- Components created using Power Apps component framework aren’t fully compatible with form footers, which causes usability issues when added to a form footer.
- Form footers aren’t included in the mobile experience or on the view and dashboard pages. This change will align the form experience with other pages in a model-driven app.
So now, main forms will no longer include the footer when a record is opened. Any out-of-box or custom controls that have been added to the form footer will no longer be available, and you’ll need to remove the fields or move the fields to the header and use the high-density header with flyout or add them onto the main form.
Tooltips for column descriptions in model-driven forms
Now the tooltips for column descriptions will be removed because Microsoft considers that the tooltips aren’t an accessible way to have access the information related to the column that means these descriptions won’t be available on mouseover
In April 2022, It will be available a fully accessible resource to replace it.
Conclusion
Do you remember whether you had used any of these resources? If yes, please check if there is a needs to make changes to your customers 😊
This article was written based on: Important changes (deprecations) coming in Power Apps, Power Automate, and customer engagement apps
Furthermore, if you like to follow the Microsoft release plans, keep your eyes on the links below:
Maykon Alves 
Leave a Reply