Merge pull request MicrosoftDocs#4407 from MicrosoftDocs/matp-2258784

Matp 2258784

Author: Mattp123

powerapps-docs/maker/TOC.yml

@@ -1116,7 +1116,7 @@
             href: ./model-driven-apps/create-edit-quick-view-forms.md
           - name: "Create a card form"
             href: ./model-driven-apps/create-card-forms.md
-        - name: Form editor overview
+        - name: Use the classic form editor
           href: ./model-driven-apps/form-editor-user-interface-legacy.md
           items:
           - name: Form properties overview
@@ -1131,8 +1131,6 @@
           href: ./model-driven-apps/main-form-presentations.md
         - name: Control access to forms
           href: ./model-driven-apps/control-access-forms.md
-        - name: Add a column to a form
-          href: ./model-driven-apps/add-field-form.md
         - name: Show or hide form elements
           href: ./model-driven-apps/visibility-options-legacy.md
         - name: Change navigation within a form

powerapps-docs/maker/data-platform/create-edit-1n-relationships.md

@@ -41,7 +41,7 @@ There are two designers you can use to create and edit 1:N (one-to-many) or N:1
 
 > [!NOTE]
 > You can also create new table relationship in your environment using the following:
-> - In model-driven apps, select **New Column** from the form editor and create a *Lookup* column. <br />More information: [Add a column to a form](../model-driven-apps/add-field-form.md)
+> - In model-driven apps, select **New Column** from the form editor and create a *Lookup* column. <br />More information: [Add, configure, move, or delete columns on a form](../model-driven-apps/add-move-or-delete-fields-on-form.md)
 > - Create a new Lookup column for the related table. <br />More information: [Create and edit columns](create-edit-fields.md)
 > - Import a solution that contains the definition of the table relationship. <br />More information: [Import, update, and export solutions](import-update-export-solutions.md)
 > - Use Power Query to create new tables and fill them with data. <br />More information: [Add data to a table in Dataverse by using Power Query](add-data-power-query.md).

powerapps-docs/maker/data-platform/create-edit-field-solution-explorer.md

@@ -57,7 +57,7 @@ You can select the following views:
 While viewing columns, in the command bar, click **New** which will open the new column form.  Some standard tables or custom tables that are included in a managed solution might not allow you to add new columns.
 
 > [!NOTE]
-> For model-driven apps you can also create a new column from the form editor. In the form editor, below the **Column Explorer** click **New Column** to create a new column. More information: [Add a column to a form](../model-driven-apps/add-field-form.md)
+> For model-driven apps you can also create a new column from the form editor. In the form editor, below the **Column Explorer** click **New Column** to create a new column. More information: [Add, configure, move, or delete columns on a form](../model-driven-apps/add-move-or-delete-fields-on-form.md)
 
 ![Solution explorer new column form](media/solution-explorer-new-field-form.png)
 
@@ -221,7 +221,7 @@ Once you have configured the column, use one of three commands in the command ba
 While [viewing columns](#view-columns), select the column you want to edit. Some standard columns or custom columns that are included in a managed solution might not allow you to edit them.
 
 > [!NOTE]
-> When editing a form, for any column already added to the form you can double-click the column to display the **Column Properties**. On the **Details** tab, click **Edit**. More information: [Add a column to a form](../model-driven-apps/add-field-form.md)
+> When editing a form, for any column already added to the form you can double-click the column to display the **Column Properties**. On the **Details** tab, click **Edit**. More information: [Add, configure, move, or delete columns on a form](../model-driven-apps/add-move-or-delete-fields-on-form.md) 
 
 After you make changes to a column, you must publish customizations. 
 

powerapps-docs/maker/model-driven-apps/form-editor-user-interface-legacy.md

@@ -18,6 +18,8 @@ search.app:
 ---
 # Overview of the model-driven app form editor user interface
 
+This article describes the classic form editor. We recommend that you use the modern form designer to create and edit your model-driven app forms. More information: [Overview of the model-driven form designer](form-designer-overview.md)
+
 The form editor displays commands in three tabs: **File**, **Home**, and **Insert**.  
 
 - [File tab](#file-tab)

powerapps-docs/maker/model-driven-apps/form-properties-legacy.md

@@ -22,6 +22,8 @@ search.app:
 
 # Model-driven app form properties 
 
+This article describes the classic solution explorer. We recommend that you use the modern form designer to edit properties for your model-driven app forms. More information: [Configure a form](create-and-edit-forms.md#configure-a-form) and [Configure model-driven app form event handlers](configure-event-handlers-legacy.md)
+
 You can access **Form properties** in solution explorer. Under **Components**, expand **Tables**, expand the table you want, and then select **Forms**. In the list of forms, open the form of type **Main**. Then on the **Home** tab, select **Form Properties**.
 
 ![Form properties](media/form-properties.png)
@@ -36,7 +38,8 @@ The following table lists the form properties:
 ||**Description**|Enter a description that explains how this form is different from other main forms. This description is only shown in the list of forms for a table in the solution explorer.|  
 ||**Form Assistant**|Select from the check box if you want to enable form assistant or view the form as expanded by default.|
 ||**Page Navigation**|You can choose not to show navigation items.<br /><br /> In forms for updated tables this means the primary name value for the row currently being viewed will not appear in the navigation bar to allow navigation to associated views.<br /><br /> In forms using the classic presentation, the navigation options to choose associated views on the left side of the form will not be shown.|  
-||**Image**|When a table has an image column and the entities’ **Primary Image** option is set, this setting will enable showing the image column in the header of this form.<br /><br /> See [Enable or disable table options](../data-platform/edit-entities.md#enable-or-disable-table-options) for more information about table options.|  ||**Display**|**Set a Max Width (in pixels)** to limit the width of the form. The default value is 1900.|  
+||**Image**|When a table has an image column and the entities’ **Primary Image** option is set, this setting will enable showing the image column in the header of this form.<br /><br /> See [Enable or disable table options](../data-platform/edit-entities.md#enable-or-disable-table-options) for more information about table options.|  
+||**Display**|**Set a Max Width (in pixels)** to limit the width of the form. The default value is 1900.|  
 ||**Display**|Enter in pixels the max width that you want for the form here.|
 |**Parameters**|**Parameters**|Each form can be opened with code using a URL. The URL may also contain data that can be passed to the form using a query string that is appended to the URL. Query strings look like this example:<br />`?p_firstName=Jim&p_lastName=Daly`<br /><br /> As a security measure, forms will not accept any unknown query string parameters. Use this parameters list to specify parameters this form should accept to support code that will pass data to the forms using a query string.<br /><br /> The name and type of data will be checked and the form won’t open if invalid query string parameters are passed to it.<br /><br />**Note:** The name cannot start with an underscore (_) or crm\_. It must start with alphanumeric  characters followed by an underscore (\_). For example, parameter_1 or 1_parameter. The name cannot contain hyphens (-), colons (:), semicolons (;), commas (,) or periods (.). <br /><br />|  
 |**Non-Event Dependencies**|**Dependent Columns**|Each event handler has a similar **Dependent Columns** property so that any columns that are needed by the script can be registered. Anyone who tries to remove the dependent columns will not be able to.<br /><br /> Some scripts operate on the form but are not configured in an event handler. Scripts that are initiated from the command bar do not have a place where dependent columns can be registered. This form property provides a place for dependent columns for those scripts to be registered.|  

powerapps-docs/maker/model-driven-apps/sub-grid-properties-legacy.md

@@ -19,45 +19,9 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Sub-grid properties for model-driven app main forms overview
+# Sub-grid properties for model-driven app main forms
 
-You can configure a sub-grid on a form to display a list of rows.  
-
-You can access **Sub-Grid properties** from the Power Apps site. 
-1.  Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
-
-2.  Expand **Data**, select **Tables**, select the table that you want, and then select the **Forms** tab. 
-
-3.  In the list of forms, open a form of type **Main**, and then select **Components**. 
-
-4.  From the Components pane, select **Subgrid**.
-
-    > [!div class="mx-imgBorder"] 
-    > ![Select sub-grid views](media/sub-grid-views.png "Select sub-grid views")
-
-5.  In **Table**, select a table whose rows you want to display in the sub-grid. The **Table** drop-down list is filtered to list only tables that are related to the current table.
-
-6.  In **Default view**, select a default view for the sub-grid. The is the view of the table selected in the Table property that will be used to get and display the list of rows in the sub-grid.
-
-7.  Select **Show related rows** to display only rows related to the current row that is displayed on the form.
-
-8.  Select **Done** to add the sub-grid to the form. The properties of the sub-grid appear in the Properties pane.
-
-    > [!div class="mx-imgBorder"] 
-    > ![sub-grid properties](media/newform-designer-sub-grid-properties.png "sub-grid properties")
-
-|Property|Description|  
-|--------------|-----------------|  
-|**Name**|**Required**: The unique name for the sub-grid that is used when referencing it in scripts. The name can contain only alphanumeric characters and underscores.|  
-|**Label**|**Required**: The localizable label for the sub-grid visible to users.|  
-|**Hide label**|Whether the label should be displayed on the form. This is required if you enable **Display Search Box**. You can also choose to have the panel header color.|  
-|**Hide on phone**|Specify whether the section should be available on phone.|
-|**Show related rows**| Sub-grid will display only rows related to the current row.<br /> If you do not select this property, the sub-grid will display rows filtered only by the default view or, if the view selector is enabled, any views the user chooses.<br /><br /> The option you choose will affect the behavior of the show list control. More information: [Show list behavior](#show-list-behavior) |  
-|**Table**|Depending on the option you choose for **Show related rows**, this list displays either:<br /><br /> - Only related rows: A list of tables that are related to this table with the name of the lookup column on that table which defines the relationship in parentheses.<br />- All row types: A list of all tables.|  
-|**Default view**|Choose the view that will be applied by default. If you do not enable any other views using the **View Selector** property. This will be the only view.<br /><br /> Use the **Edit** button to open the default view for editing. Use the **New** button to create a new view to use for this sub-grid.|  
-|**Allow users to change view**|When selected, app users can change from the Default view to another view of the table selected in the Table property.|
-
-## Sub-grid properties for model-driven app main forms: Classic
+This article describes the classic form editor. We recommend that you use the modern form designer to create and edit sub-grids for your model-driven app forms. More information: [Add and configure a subgrid component on a form](form-designer-add-configure-subgrid.md)
 
 You can configure a sub-grid on a form using the classic form designer to display a list of rows or a chart. Select **Show Chart Only** on the **Display** tab to show a chart instead of a list.
 

powerapps-docs/maker/model-driven-apps/tab-properties-legacy.md

@@ -21,30 +21,7 @@ search.app:
 ---
 # Tab properties for model-driven app forms overview
 
- In the body of a form, tabs provide horizontal separation. Tabs have a label that can be displayed. If the label is displayed, tabs can be expanded or collapsed to show or hide their content by choosing the label.  
-  
- Tabs contain up to three columns and the width of each column can be set to a percentage of the total width. When you create a new tab, each column is pre-populated with a section.  
-
-You can access **Tab properties** from the Power Apps site. 
-1.  Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
-
-2.  Expand **Data**, select **Tables**, select the table that you want, and then select the **Forms** tab.  
-
-3.  In the list of forms, open the form of type **Main**. Then select one of the tabs on the form to view the tab properties.
-
-|Property|Description|  
-|--------------|-----------------|  
-|**Tab label**|**Required**: The localizable label for the tab visible to users.|  
-|**Name**|**Required**: The unique name for the tab that is used when referencing it in scripts. The name can contain only alphanumeric characters and underscores.|  
-|**Expand this tab by default**|The tab state can toggle between expanded or collapsed using form scripts or by people selecting the label. Choose the default state for the tab.|  
-|**Hide tab**|Showing the tab is optional and can be controlled using scripts. Choose whether to make the tab visible. More information: [Visibility options](visibility-options-legacy.md)|  
-|**Hide on phone**|Choose if you want the tab to be available on the phone. For a condensed version of this form on phone screens, you can hide the tab.|  
-|**Formatting**|Tabs may have up to three columns. Use these options to set the number of tabs and what percentage of the total width they should fill.|  
-
-  > [!div class="mx-imgBorder"] 
-  > ![tab-properties](media/newform-tab-properties.png "Tab properties")
-
-## Tab properties for model-driven app main forms: Classic
+This article describes the classic form editor. We recommend that you u se the modern form designer to add and edit tabs for your model-driven app forms. More information: [Add, configure, move, or delete tabs on a form](add-move-or-delete-tabs-on-form.md)
 
 These are the properties available to configure when using a tab on a form using the classic form designer. The following table shows properties that you can set for tabs on the form: