Important changes (deprecations) coming in Power Apps, Power Automate, and customer engagement apps

The announcements and deprecations described in this article apply to Power Apps, Power Automate, and customer engagement apps (Dynamics 365 Sales, Dynamics 365 Marketing, Dynamics 365 Field Service, and Dynamics 365 Project Service Automation).

Administrators and IT professionals should use this information to prepare for future releases. This article was first published on June 27, 2017.

 Important

“Deprecated” means we intend to remove the feature or capability from a future major release. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few months or years. After removal, the feature or capability will no longer work. We are notifying you now so you have sufficient time to plan and update your code before the feature or capability is removed.

Low-density headers in model-driven apps won’t be supported with the 2021 release wave 2

With the upcoming 2021 release wave 2 (public preview in August 2021 and GA in October 2021), the low-density header option, and runtime experience won’t be supported in model-driven app forms.

Why is this needed?

  • 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 (small to very-wide)

Impact

Any current form that is configured to be “low-density” will be automatically updated to render in a high-density with flyout mode in a model driven app. Here is an example of high-density header with flyout:

Header flyout with high-density header

Action required by you

To meet the October 2021 deadline, you will need to 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 will no longer honor this setting at runtime, and will default to high-density with flyout.

Form footers in model-driven app won’t be supported with the 2021 release wave 2

With the upcoming 2021 release wave 2 (public preview in August 2021 and GA in October 2021), form footers won’t be supported in a model-driven app form.

Why is this needed?

  • The footer does not meet the Microsoft Web Content Accessibility Guidelines (WCAG) 2.0 compliance for accessibility.
  • Data density is highly impacted by the form footer and does not support a good customer experience. Controls are not discoverable and lead to many customer usability issues.
  • Makers have moved away from adding controls into the footer and there is 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 cause usability issues when added to a form footer.
  • Form footers are not 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.

Impact

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 if they are no longer necessary or move the fields to the header and use the high-density header with flyout or add them onto the main form. The recommended approach is to move fields that users need to access regardless of the form tab a user is on to the header and set it to use the high-density header with flyout. If there is only one tab, the recommendation is to move them into a new section on the form.

Action required by you

  • To meet the October 2021 deadline, you will need to move fields or controls added to a form footer to either the header or a section on the form.
  • If you do nothing, the footer fields or controls that you have added will no longer render on the form and will not be available to your users.

The out of box fields currently on the footer will be removed and included on the form as part of the 2021 release wave 2 updates. So, you will not lose status, unsaved changes or the option to open a form in a new window. The Save option is already available in the command bar and is always visible to the user.

While we understand that these types of changes can be disruptive for makers that use the footer today, we always evaluate the experiences to ensure they provide a modern experience that improves usability, support accessibility requirements, and improves discoverability for highly used fields and controls on a page.

Model-driven app controls deprecation

With the upcoming 2021 release wave 1 (public preview in February 2021 and GA in April 2021), some older controls for model-driven apps will be deprecated. These controls include Flip Switch, Calendar Control (V1), Linear Slider, Radial Knob, Arc Knob, Linear Gauge; along with the Website Preview control, MultiSelectPicklistControl (V1), and the Flip Label.

Why is this needed?

  • These controls are outdated and don’t conform to our current standards for useability and accessibility.
  • For example, we’ve received feedback that the Flip Label control is difficult to determine its intended use and users commonly don’t see the options available to choose from, such as “yes / no” or “enable / disable.”

Impact

  • Starting April 2021, these controls can no longer be added to forms.
  • For instances of Flip Label control, the control will be transitioned to a drop down.
  • For all other controls, they will continue to work within existing forms until April 2022.

Action required by you

We will not make other changes to forms or controls. Makers are encouraged to make updates:

  • Use the Toggle control as a replacement for Flip Label and Flip Switch.
  • Use the Calendar Control (V2) as a replacement for Calendar Control (V1).
  • Evaluate other deprecated controls to determine if they’re still useful within existing forms.

Microsoft Dynamics 365 Email Router is deprecated

The Microsoft Dynamics 365 Email Router will no longer function on April 21, 2021. For information on migrating email routing functionality to use the server-side synchronization feature, see: Migrate settings from the Email Router to server-side synchronization.

The Microsoft Dynamics 365 application for Windows is deprecated

Effective April 2021, the Microsoft Dynamics 365 app for Windows that lets you run customer engagement apps (such as Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Marketing) is deprecated. Microsoft will continue to provide security and other critical updates for the Microsoft Dynamics 365 app for Windows until January 29, 2021, but will not release any another features or functionalities for the app. After April 1, 2021, the app will be removed from the Microsoft Store, and it will not be supported.

We recommend that you start using your web browser as soon as possible to run your customer engagement apps (such as Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Marketing) on Windows to take advantage of the ongoing improvements for the web app.

Scroll to Top