Merge pull request #6166 from MicrosoftDocs/jdaly-main-remove-formContext.ui.footerSection

Jdaly main remove form context.UI.footer section

Author: JimDaly

.openpublishing.redirection.json

@@ -1,5 +1,20 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection.md",
+      "redirect_url": "formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/getVisible.md",
+      "redirect_url": "../formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/setVisible.md",
+      "redirect_url": "../formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
     {
       "source_path": "powerapps-docs/developer/data-platform/outlook-client/sample-create-retrieve-outlook-filters.md",
       "redirect_url": "../data-platform/org-service/samples/create-retrieve-outlook-filters",

powerapps-docs/developer/model-driven-apps/TOC.yml

@@ -512,13 +512,6 @@
         href: clientapi/reference/formcontext-ui/setFormEntityName.md
       - name: setFormNotification
         href: clientapi/reference/formcontext-ui/setFormNotification.md
-    - name: formContext.ui.footerSection
-      href: clientapi/reference/formcontext-ui-footerSection.md
-      items: 
-      - name: getVisible
-        href: clientapi/reference/formcontext-ui-footerSection/getVisible.md
-      - name: setVisible
-        href: clientapi/reference/formcontext-ui-footerSection/setVisible.md
     - name: formContext.ui.formSelector
       href: clientapi/reference/formcontext-ui-formselector.md
       items:

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection.md

@@ -4,7 +4,7 @@ description: "Provides properties and methods to retrieve information about the
 ms.author: jdaly
 author: adrianorth
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 04/07/2022
 ms.reviewer: jdaly
 ms.topic: "reference"
 applies_to: "Dynamics 365 (online)"
@@ -52,6 +52,9 @@ Provides properties and methods to retrieve information about the user interface
 |[setFormNotification](formContext-ui/setFormNotification.md)|[!INCLUDE[formContext-ui/includes/setFormNotification-description.md](formContext-ui/includes/setFormNotification-description.md)]|
 
 
+## formContext.ui.footerSection removed
+
+The `formContext.ui.footerSection` was removed in October of 2021. More information: [Form footers in model-driven apps won't be supported with the 2021 release wave 2](/power-platform/important-changes-coming#form-footers-in-model-driven-apps-wont-be-supported-with-the-2021-release-wave-2)
 
 ### Related topics
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/getVisible.md

@@ -2,7 +2,7 @@
 title: "Productive main form design in model-driven apps | MicrosoftDocs"
 description: Learn how to design productive main forms for your model-driven apps.
 ms.custom: ""
-ms.date: 04/27/2021
+ms.date: 04/07/2022
 ms.reviewer: "Mattp123"
 
 ms.suite: ""
@@ -75,7 +75,6 @@ The following image shows the layout of a Unified Interface application.
 - The form body is the area on the form that should be used to interact with data of the [record](model-driven-app-glossary.md#record) and any related records that are essential to completing a task. We recommend that you limit the data to the top tasks that need to be done on the first tab and move secondary tasks to additional tabs. [building forms based on specific business needs and roles](design-considerations-main-forms.md) should also be considered when designing your application.
 
 If some data is rarely used you should consider building another form that can be accessed when a user needs to reference that data or information.
-- The form footer displays the form status and commands for saving and displaying the form in a new pop-out window. Only the form footer width can be customized.
 
 > [!IMPORTANT]
 > [Form footers are deprecated](/power-platform/important-changes-coming#form-footers-in-model-driven-apps-wont-be-supported-with-the-2021-release-wave-2) with the 2021 Release Wave 2 (August 2021 Preview / October 2021 GA). Remove any controls you have added out of the footer.
@@ -196,7 +195,7 @@ More information: [Create a model-driven app quick view form to view information
 
 There are many times when you need to build an experience that focuses the user on the task at hand without additional distraction that might cause inefficiency. This is especially important when you're working with tables and records that have global components, which are created and automatically added to forms regardless of the task you're trying to build. Although this provides a shareable and easy-to-build infrastructure that drives consistency across an app, it does at times provide unnecessary distraction.
 
-Form display options should be used when you want to lessen the number of actions, focus a user to complete a task, and reduce clutter by removing unnecessary components. Components that can be removed from a form include the command bar, the header body, the form tabs, and the form footer.
+Form display options should be used when you want to lessen the number of actions, focus a user to complete a task, and reduce clutter by removing unnecessary components. Components that can be removed from a form include the command bar, the header body, and the form tabs.
 
 All these types of options are only available via the client API and manual formxml updates. Manual formxml manipulation can cause issues importing solutions if done incorrectly. Remove global form components carefully when designing your form.
 
@@ -220,10 +219,6 @@ In this example, the tabs have been removed. This can be helpful when you build
 
 :::image type="content" source="media/form-no-tabs.png" alt-text="Form without tabs shown in an app.":::
 
-In some scenarios where you want more data density, and don't use or need the form footer, you can easily remove it to provide more data and information on the form. This can also help drive consistency as users move from dashboards and view pages where footers aren't included on the page. In this example, the form footer has been removed to reduce clutter and drive data density. More information: [setVisible (Client API reference)](../../developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/setVisible.md)
-
-:::image type="content" source="media/form-no-footer.png" alt-text="Form without a footer shown in an app.":::
-
 ### Form display option to use the entire space of a tab
 
 In many scenarios, a form might exist with a tab and a single control, and you want that control to take up the entire available space within the body of the form on that tab. This can be done by using the **form display option** that allows the first control on a page in a tab to expand the full height and width of the form. All existing reflow rendering across view port sizes from large to small is honored, and will behave like a regular form except that the control will use the entire space. In this example, the Dynamics 365 Marketing application supports a full tab layout for the customer journey experience. The command bar is removed to further reduce clutter and ensure that the user is focused on the task of managing customer journeys in the application. More information: [setContentType (Client API reference)](../../developer/model-driven-apps/clientapi/reference/formContext-ui-tabs/setContentType.md)

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/includes/getVisible-description.md

@@ -2,7 +2,7 @@
 title: "Show or hide model-driven app form elements with Power Apps | MicrosoftDocs"
 description: "Learn how to display or hide from elements, such as tabs, sections, or columns"
 ms.custom: ""
-ms.date: 08/27/2020
+ms.date: 04/07/2022
 ms.reviewer: ""
 
 ms.suite: ""
@@ -43,9 +43,8 @@ In Unified Interface, for sections where columns don’t span more than one colu
 
 ## Client API methods for controlling the visibility of form elements
 
-For information about how to change the form element show or hide status for the header, command bar, footer, and tabs at app runtime, see these client API reference articles:
+For information about how to change the form element show or hide status for the header, command bar, and tabs at app runtime, see these client API reference articles:
 - [formContext.ui.headerSection item (Client API reference)](../../developer/model-driven-apps/clientapi/reference/formContext-ui-headerSection.md)
-- [formContext.ui.footerSection item (Client API reference)](../../developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection.md)
 - [formContext.ui.tabs (Client API reference)](../../developer/model-driven-apps/clientapi/reference/formContext-ui-tabs.md)
 
 ## Next steps