Merge pull request #5896 from MicrosoftDocs/matp-2615139

Matp 2615139

Author: Mattp123

powerapps-docs/maker/canvas-apps/functions/function-filter-lookup.md

@@ -2,7 +2,6 @@
 title: Filter, Search, and LookUp functions in Power Apps (contains video)
 description: Reference information including syntax and examples for the Filter, Search, and LookUp functions in Power Apps.
 author: gregli-msft
-
 ms.topic: reference
 ms.custom: canvas
 ms.reviewer: tapanm
@@ -116,7 +115,7 @@ The following examples use the **IceCream** [data source](../working-with-data-s
 
 In many apps, you can type one or more characters into a search box to filter a list of records in a large data set. As you type, the list shows only those records that match the search criteria.
 
-The examples in the rest of this topic show the results of searching a list, named **Customers, that contain this data:
+The examples in the rest of this topic show the results of searching a list, named **Customers**, that contain this data:
 
 ![Search on customers.](media/function-filter-lookup/customers.png "Search on customers")
 

powerapps-docs/maker/data-platform/data-platform-create-entity.md

@@ -17,7 +17,6 @@ search.app:
 
 # Create a custom table
 
-
 In Power Apps, a *table* defines information that you want to track in the form of records, which typically include properties such as company name, ___location, products, email, and phone. You can then surface that data by developing an app that refers to the table. Power Apps offers standard "out-of-the-box" tables to cover typical scenarios within an organization (such as tracking appointments), but there may be times when you need to create custom tables to store data that's specific to your organization.
 
 Watch this video for a quick overview about how to create a table:
@@ -42,10 +41,10 @@ Sign in to Power Apps at [https://make.powerapps.com](https://make.powerapps.com
 
     |Section  |Column  |Description  |
     |---------|---------|---------|
-    |Required columns   | **Display name ***      | This is the singular name for the table that will be shown in the app. This can be changed later.     |
-    |Required columns      |  **Plural display name ***        | This is the plural name for the table that will be shown in the app. This can be changed later.      |
-    |Required columns     |  **Display Name *** (Primary column)     | By default, every table contains a Primary Field, which is used by lookup columns when establishing relationships with other tables. Typically the primary column stores the name or primary description of the data stored in the table. You may update the name and display name of the primary column before saving the table for the first time. Also, observe that the primary column also has its own **Name** box, which functions similarly to the table name described above. The primary column name is autopopulated when a display name is entered, uses the same prefix as the table, and cannot be changed after the table is created.      |
-    |Required columns      | **Name &#42;**    |  This column is pre-populated based on the **Primary Column Display name** you enter. It includes the customization prefix for the Dataverse solution publisher. You cannot change this after the table is saved. <br /> <br /> In order for the table name to work with [Dynamics 365 for Customer Service embedded knowledge search](/dynamics365/customer-engagement/customer-service/set-up-knowledge-management-embedded-knowledge-search), the maximum table name length including the publisher prefix can’t exceed 24 characters.         |
+    |Required columns   | **Display name**      | This is the singular name for the table that will be shown in the app. This can be changed later.     |
+    |Required columns      |  **Plural display name**        | This is the plural name for the table that will be shown in the app. This can be changed later.      |
+    |Required columns     |  **Display name** (Primary Name Column)     | By default, every table contains a **Primary Name Column**, which is used by lookup columns when establishing relationships with other tables. Typically the primary name column stores the name or primary description of the data stored in the table. You may update the name and display name of the primary name column before saving the table for the first time. Also, observe that the primary name column also has its own **Name** box, which functions similarly to the table name described above. The primary name column name is autopopulated when a display name is entered, uses the same prefix as the table, and cannot be changed after the table is created.      |
+    |Required columns      | **Name**    |  This column is pre-populated based on the **Primary Column Display name** you enter. It includes the customization prefix for the Dataverse solution publisher. You cannot change this after the table is saved. <br /> <br /> In order for the table name to work with [Dynamics 365 for Customer Service embedded knowledge search](/dynamics365/customer-engagement/customer-service/set-up-knowledge-management-embedded-knowledge-search), the maximum table name length including the publisher prefix can’t exceed 24 characters.         |
     | Required columns  | **Enable attachments**  | Adds the attachments control to the table. The control is used to add or remove files and notes to records. Enabling this option lets users add files, such as document files from their computer or existing photos from a mobile device. Attached files can be up to 10 MB in size. Once this option is set, it can’t be changed after the table is created.   |
     |**Description**     | **Description**      | Expand **More settings** > **Description**.  You can enter a description for your table if you wish. Descriptions are helpful if other people will use this table.     |
     |**Table type and ownership**   |  **Choose table type**    | Switch the table type to **Activity table** to create tables that can manage tasks.      |
@@ -64,7 +63,7 @@ Sign in to Power Apps at [https://make.powerapps.com](https://make.powerapps.com
     | **Dynamics 365 for Outlook**  | **Enable offline capabilities**  | Enables row data for this table to be available while the Dynamics 365 for Outlook application is not connected to the network.  |
 
 4. Select **Create**.
-     
+
 On the table details page, observe that the table is now being provisioned in the background. Once provisioning is completed, your table will be saved and available for use in apps. Fields, relationships, and keys can be added to your table at any time (even while provisioning is still in progress), but views, forms, charts, dashboards, and business rules can only be added to the table after provisioning is completed.
 
 ## Next steps

powerapps-docs/maker/model-driven-apps/add-edit-app-components.md

@@ -56,7 +56,7 @@ The app designer has two main areas. On the left side is the canvas, where app c
  > [!div class="mx-imgBorder"]
  > ![App designer components.](../model-driven-apps/media/app-designer-canvas-components-tab.png "App designer components")  
   
- The canvas includes areas for the **Site Map**, *Business Process Flow**, **Dashboards**, and **Tables**.
+ The canvas includes areas for the **Site Map**, **Business Process Flow**, **Dashboards**, and **Tables**.
 
  After the tables are in place, select each table and add the required table assets such as forms, views, and charts to it.
 

powerapps-docs/maker/model-driven-apps/create-edit-views.md

@@ -50,7 +50,7 @@ Views can be developed through the table designer or the app designer.
 
 ## Types of views  
 
-There are three types of views: *personal*, *system, and *public*.
+There are three types of views: *personal*, *system*, and *public*.
 
 - **Personal view** - Personal views are owned by individuals and only visible to that person unless they share their personal views with others.
 - **System view** - As a system administrator or system customizer, you can edit system views. System views are special views the application depends on, which exist for system tables or are automatically created when you create custom tables. These views have specific purposes and some additional capabilities.

powerapps-docs/maker/model-driven-apps/monitor-form-checker.md

@@ -75,7 +75,7 @@ There are two ways to open a Monitor session.
 
 ## Use Monitor to understand form behavior
 
-For each row with Monitor, detailed information about the form event can be reviewed. For example, imagine you have a question about an error taking place within the form. You go to that form in the app and select the appropriate form component. Then return to the browser with Monitor enabled and review the results either with or without filtering.  In this case, there is an error on the composite control.  By expanding the Properties,** you can learn more about the event itself.
+For each row with Monitor, detailed information about the form event can be reviewed. For example, imagine you have a question about an error taking place within the form. You go to that form in the app and select the appropriate form component. Then return to the browser with Monitor enabled and review the results either with or without filtering.  In this case, there is an error on the composite control.  By expanding areas of the **Details**, you can learn more about the event itself.
 
 > [!div class="mx-imgBorder"] 
 > ![Monitoring a related menu.](media/monitor-formchecker-related-menu.png)

powerapps-docs/maker/model-driven-apps/share-model-driven-app.md

@@ -188,15 +188,15 @@ To get the direct link to an app:
 
 These predefined roles are available with Dataverse.
 
-|Security role  |*Privileges  |Description |
+|Security role  |Privileges<sup>1</sup>  |Description |
 |---------|---------|---------|
 |Environment Maker     |  None       | Can create new resources associated with an environment including apps, connections, custom APIs, gateways, and flows using Power Automate. However, does not have any privileges to access data within an environment. More information: [Environments overview](https://powerapps.microsoft.com/blog/powerapps-environments/)        |
 |System Administrator     |  Create, Read, Write, Delete, Customizations, Security Roles       | Has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Can view all data in the environment. More information: [Privileges required for customization](/dynamics365/customer-engagement/customize/privileges-required-customization)        |
 |System Customizer     | Create (self), Read (self), Write (self), Delete (self), Customizations         | Has full permission to customize the environment. However, can only view records for environment tables that they create. More information: [Privileges required for customization](/dynamics365/customer-engagement/customize/privileges-required-customization)        |
 |Basic User     |  Read, Create (self), write (self), delete (self)       | Can run an app within the environment and perform common tasks for the records that they own.        |
 |Delegate     | Act on behalf of another user        | Allows code to run as another user or impersonate.  Typically used with another security role to allow access to records. More information: [Impersonate another user](/dynamics365/customer-engagement/developer/org-service/impersonate-another-user)        |
 
-*Privilege is global scope unless specified otherwise.
+<sup>1</sup>Privilege is global scope unless specified otherwise.
 
 ## Use Azure Active Directory groups to manage access
 

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

@@ -27,20 +27,20 @@ search.app:
 ![special-properties-dialog.](media/special-properties.png)
 
 <a name="BKMK_LookupFieldProperties"></a>  
- 
+
 ## Lookup column properties  
 
 > [!NOTE]
->  The options described in the table below are available only for single-table lookup columns.  
+> The options described in the table below are available only for single-table lookup columns.  
   
 |Section|Property|Description|  
 |-------------|--------------|-----------------|  
-|**Related Rows Filtering**|**Only show rows where**|When this is enabled, the rows that display when users search for a row will have additional filtering applied. This helps provide more relevant searches when setting the value of the lookup.<br /><br /> By default, this is turned off.<br /><br /> The relationship combinations that are possible when you filter related rows are listed in the table following this one.*<br /><br /> The first list is populated with all the potential relationships you can use to filter this lookup. Select one.<br /><br /> The second list is then populated with all relationships that connect the related table (selected in first list) to the target table. Select one.<br /><br /> Select the **Allow users to turn off filter** check box to give users the option to turn off the filter you define here.<br /><br /> When users select the **Look Up More Rows** option while setting the value for a lookup, they see this dialog box.<br /><br /> ![look-up-more-records.](media/crm-ua-v-8-1-look-up-more-records.png) <br /><br /> If you’ve selected the **Allow users to turn off filter** option while configuring the lookup column, users will see the check box to turn off the filter.  This makes it possible for them to see a wider range of rows. If you want to make sure that users only see a limited range of rows defined by this filter, clear the  **Allow users to turn off filter** check box.|  
+|**Related Rows Filtering**|**Only show rows where**|When this is enabled, the rows that display when users search for a row will have additional filtering applied. This helps provide more relevant searches when setting the value of the lookup.<br /><br /> By default, this is turned off.<br /><br /> The relationship combinations that are possible when you filter related rows are listed in the table following this one.<br /><br /> The first list is populated with all the potential relationships you can use to filter this lookup. Select one.<br /><br /> The second list is then populated with all relationships that connect the related table (selected in first list) to the target table. Select one.<br /><br /> Select the **Allow users to turn off filter** check box to give users the option to turn off the filter you define here.<br /><br /> When users select the **Look Up More Rows** option while setting the value for a lookup, they see this dialog box.<br /><br /> ![look-up-more-records.](media/crm-ua-v-8-1-look-up-more-records.png) <br /><br /> If you’ve selected the **Allow users to turn off filter** option while configuring the lookup column, users will see the check box to turn off the filter.  This makes it possible for them to see a wider range of rows. If you want to make sure that users only see a limited range of rows defined by this filter, clear the  **Allow users to turn off filter** check box.|  
 |**Additional Properties**|**Display Search Box in lookup dialog**|You can choose not to display the search box in the lookup dialog.|  
 ||**Default View**|This view is used to filter the results of the inline search and set the default view shown in the lookup dialog when users select the **Look Up More Rows** option.<br /><br /> The default view also controls which columns are included in the inline lookup.<br /><br /> For lookups that only allow selection of a single table type, the columns displayed in the inline lookup are set to be the first two columns included in the default view. In this example, **Main Phone** and **Email** are the first two columns in the default view configured for an account lookup.<br /><br /> For system lookups that allow for multiple table types, the first two columns of the table lookup view are shown.|  
 ||**View Selector**|You can choose from three options:<br /><br /> -   **Off**: Don’t allow users to choose a different view.<br />-   **Show All Views**: All views are available.<br />-   **Show Selected Views**: When you choose this option you can use the Ctrl key and your cursor to choose which views to show. The Lookup view for the table can’t be de-selected.|  
 
- **\*Possible Relationship Combinations**  
+### Possible relationship combinations
 
 |First list relationship|Second list relationship|Available?|  
 |-----------------------------|------------------------------|----------------|  
@@ -67,7 +67,8 @@ search.app:
 
 <a name="BKMK_MultipleLinesOfTextProperties"></a>   
 
-### Multiple lines of text column properties  
- Multiple lines of text and single line of text columns that use the `Text Area` format have a **Row Layout** property. With this property you can specify a value for **Number of Rows** or select **Automatically expand to use available space**.  
+### Multiple lines of text column properties
+
+Multiple lines of text and single line of text columns that use the `Text Area` format have a **Row Layout** property. With this property you can specify a value for **Number of Rows** or select **Automatically expand to use available space**.  
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/model-driven-apps/use-main-form-and-components.md

@@ -144,7 +144,7 @@ You can add iFrames to a form to integrate content from another website within a
 
  To enable editing navigation, you must first select **Navigation** from the **Select** group on the **Home** tab.  
 
- In the Relationship Explorer,** you can filter by 1:N (one-to-many) or N:N (many-to-many) relationships, or view all available relationships. The **Only show unused relationships checkbox** is disabled and selected. So you can only add each relationship one time.  
+ In the Relationship Explorer, you can filter by 1:N (one-to-many) or N:N (many-to-many) relationships, or view all available relationships. The **Only show unused relationships checkbox** is disabled and selected. So you can only add each relationship one time.  
 
  To add a relationship from the **Relationship Explorer** just double-click it and it will be added below the currently selected relationship in the navigation area. Double-click a relationship in the navigation area and you can change the label on the **Display** tab. On the **Name** tab, you can see information about the relationship. Use the **Edit** button to open the definition of the table.  
 

powerapps-docs/teams/integrate-planner.md

@@ -2,7 +2,6 @@
 title: Integrate your Teams Power App with Planner (contains video)
 description: Learn how to make your Power Apps in Teams work with Planner.
 author: joel-lindstrom
-
 ms.topic: conceptual
 ms.custom: 
 ms.date: 08/25/2021
@@ -37,7 +36,7 @@ In this section, we'll create a new Teams team and then create an app within tha
 
 1. To create a new team, select the **Teams** tab > select **Join or create a team** > select **Create Team** > select **From Scratch** > select **Public**, and give the team a name such as "Planner Integration". And then, select **Create**.
 
-1. Select and add any members in your organization that you'd like to add to the team for testing purposes, and select *Add**.
+1. Select and add any members in your organization that you'd like to add to the team for testing purposes, and select **Add**.
 
 1. Select **Close**.