Feature taken out - Form footer

In this mini-series, the author revisits retired features, and this time they look at the Form footer feature. The feature was removed as part of the 2021 release wave 2, and the reason given was that it didn't meet the Microsoft Web Content Accessibility Guidelines (WCAG) 2.0 compliance for accessibility. As a result, any out-of-the-box or custom controls that have been added to the form footer will no longer be available, and users will need to move the fields to the header or onto the main form.

The recommended approach is to move essential fields to the header and set it to use the high-density header with flyout. If there's only one tab, the recommendation is to move them into a new section on the form. The out-of-the-box fields currently on the footer are removed and included on the form as part of the 2021 release wave 2 updates, so you don't lose status, unsaved changes, or the option to open a form in a new window. Sometimes, businesses might want a similar footer-like UI, in which case, users can use a web resource or PCF control and keep it inside the entity form.

The post concludes by asking readers if they've encountered any features that they or their users miss and how they've managed the situation.

The origin of this blog post is a question on Stack Overflow, which the author links to in the post.