Merge pull request MicrosoftDocs#4389 from MicrosoftDocs/terminology-updates-mda

Terminology updates model-driven apps

Author: Nkrb

powerapps-docs/developer/model-driven-apps/actions-visualizations-charts.md

@@ -30,7 +30,7 @@ To perform actions on an organization-owned visualization (`SavedQueryVisualizat
   > [!NOTE]
   >  After updating an organization-owned visualization, you must publish the table definitions changes to make it visible across the organization by using the <xref:Microsoft.Crm.Sdk.Messages.PublishAllXmlRequest> message. Alternatively, whenever you publish a table, all the unpublished organization-owned visualizations that are attached to the table are published automatically.  
   
-- Query and retrieve all the organization-owned visualizations that are attached to a table using the `SavedQueryVisualization.PrimaryEntityTypeCode`. Multiple organization-owned visualizations can be attached to a single table. For a list of tables with which you can attach a visualization, see [Tables Supported for visualizations](view-data-with-visualizations-charts.md#SupportedVisualizationEntities). For a code sample that demonstrates how to retrieve all the organization-owned visualizations attached to an table, see [Sample: Retrieve all charts attached to a table](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/RetrieveChartsAttachedToEntity).
+- Query and retrieve all the organization-owned visualizations that are attached to a table using the `SavedQueryVisualization.PrimaryEntityTypeCode`. Multiple organization-owned visualizations can be attached to a single table. For a list of tables with which you can attach a visualization, see [Tables Supported for visualizations](view-data-with-visualizations-charts.md). For a code sample that demonstrates how to retrieve all the organization-owned visualizations attached to an table, see [Sample: Retrieve all charts attached to a table](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/RetrieveChartsAttachedToEntity).
 
   > [!NOTE]
   >  You cannot change or update a visualization to attach it with a different table after you have created the visualization. It implies that the `SavedQueryVisualization.PrimaryEntityTypeCode` is not valid for the update action on the organization-owned visualization.
@@ -49,7 +49,7 @@ To perform actions on an organization-owned visualization (`SavedQueryVisualizat
 
 - Create, retrieve, update, and delete a user-owned visualization. More information: [Create a visualization](create-visualization-chart.md)  
 
-- Query and retrieve all the user-owned visualizations that are attached to a table using the `UserQueryVisualization.PrimaryEntityTypeCode`. Multiple user-owned visualizations can be attached to a table. For a list of tables with which you can attach a visualization, see [Tables supported for visualizations](view-data-with-visualizations-charts.md#SupportedVisualizationEntities).  
+- Query and retrieve all the user-owned visualizations that are attached to a table using the `UserQueryVisualization.PrimaryEntityTypeCode`. Multiple user-owned visualizations can be attached to a table. For a list of tables with which you can attach a visualization, see [Tables supported for visualizations](view-data-with-visualizations-charts.md).  
 
   > [!NOTE]
   >  You cannot change or update a visualization to attach it with a different table after you have created the visualization. It implies that the `UserQueryVisualization.PrimaryEntityTypeCode` is not valid for the update action on the user-owned visualization.

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/consider-disabling-navbar-programmatically-opening-entity-forms-views.md

@@ -1,6 +1,6 @@
 ---
-title: "Consider disabling NavBar when programmatically opening entity forms or views | MicrosoftDocs"
-description: "Opening up entity forms or views with a URL, could lead to slower client performance on high latency networks when the navigation bar (NavBar) is enabled."
+title: "Consider disabling NavBar when programmatically opening forms or views | MicrosoftDocs"
+description: "Opening up forms or views with a URL, could lead to slower client performance on high latency networks when the navigation bar (NavBar) is enabled."
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -13,15 +13,15 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 3/04/2019
+ms.date: 04/14/2021
 ms.author: jowells
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
 ---
-# Consider disabling NavBar when programmatically opening entity forms or views
+# Consider disabling NavBar when programmatically opening forms or views
 
 **Category**: Design, Performance
 
@@ -31,15 +31,17 @@ search.app:
 
 ## Symptoms
 
-Opening up entity forms or views with a URL, could lead to slower client performance on high latency networks when the navigation bar (NavBar) is enabled.
+Opening up forms or views with a URL, could lead to slower client performance on high latency networks when the navigation bar (NavBar) is enabled.
 
 <a name='guidance'></a>
 
 ## Guidance
 
-Determine if your users need to have the full navigation bar when creating customizations that open entity forms or views through a URL. In most cases, users click on a link to open an entity form, do some quick work, and then close the record.  Disabling the navigation bar will lower the amount of resources to be loaded which lowers the number of network requests being made.  
+Determine if your users need to have the full navigation bar when creating customizations that open forms or views through a URL. In most cases, users selects on a link to open a form, do some quick work, and then close the record.  Disabling the navigation bar will lower the amount of resources to be loaded which lowers the number of network requests being made.  
 
-When constructing URLs to open up entity forms or views, implement `navbar=off` within your query string parameters for the `main.aspx` page. The following example opens an Account entity form with the navigation bar disabled.
+[!INCLUDE[cc-terminology](../../../data-platform/includes/cc-terminology.md)]
+
+When constructing URLs to open up forms or views, implement `navbar=off` within your query string parameters for the `main.aspx` page. The following example opens an Account form with the navigation bar disabled.
 
 ```JavaScript
 function disableNavBar() {
@@ -58,7 +60,7 @@ function disableNavBar() {
 > [!WARNING] 
 > These scenarios should be avoided. 
 
-Keeping the navigation bar (NavBar) enabled does not mean users will experience performance issues. However, it does mean that additional resources must be loaded on the entity form or view which does require additional network requests.  It has been observed on highly latent networks this can lead to a poor user experience.
+Keeping the navigation bar (NavBar) enabled does not mean users will experience performance issues. However, it does mean that additional resources must be loaded on the form or view which does require additional network requests.  It has been observed on highly latent networks this can lead to a poor user experience.
 
 An example of a constructed URL with the NavBar enabled is as follows
 

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/index.md

@@ -26,6 +26,8 @@ search.app:
 
 This list below contains all of the Best practices and guidance of client side scripting for model-driven apps.
 
+[!INCLUDE[cc-terminology](../../../data-platform/includes/cc-terminology.md)]
+
 |Best Practice  |Description  |
 |---------|---------|
 |[Avoid using window.top](avoid-window-top.md)     |Describes how to avoid script errors and incorrect application behavior associated with using window.top in JavaScript customizations.         |

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/remove-deactivated-disabled-configurations.md

@@ -35,6 +35,8 @@ Deactivated or disabled customizations should be removed from a solution to impr
 
 <a name='guidance'></a>
 
+[!INCLUDE[cc-terminology](../../../data-platform/includes/cc-terminology.md)]
+
 ## Guidance
 
 Ensure that each solution component that is deactivated, or disabled, has been done so intentionally.  If so and will no longer be utilized, consider removing it from the solution to prevent confusion for users and system customizers. These components include:
@@ -44,7 +46,7 @@ Ensure that each solution component that is deactivated, or disabled, has been d
 - Record Creation and Update Rules
 - SLAs
 
-As well as Entity components such as:
+As well as table components such as:
 
 - Forms
 - Views

powerapps-docs/developer/model-driven-apps/best-practices/index.md

@@ -13,7 +13,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 12/12/2018
+ms.date: 04/14/2021
 ms.author: jowells
 search.audienceType: 
   - developer
@@ -27,6 +27,8 @@ search.app:
 Model-driven apps is a component-focused approach to app development which can be extended by a developer to achieve a much more
 tailored experience. While customizing model-driven apps, a developer should be aware of the established guidance and best practices. 
 
+[!INCLUDE[cc-terminology](../../data-platform/includes/cc-terminology.md)]
+
 Within this section you will learn about the issues we have identified, their impact, and understand the guidance to resolve them. We will explain the background about why things should be done in a certain way and avoid potential problems in the future. This can benefit the usability, supportability, and performance of your environment. The guidance documentation supports the existing information within the Developer and Administration guides.
 
 > [!NOTE]
@@ -38,7 +40,7 @@ Within this section you will learn about the issues we have identified, their im
 The documentation targets the following customization types:
 
 - Model-driven app design
-- Entity form design
+- Form design
 - Client scripting
 - Web resources
 

powerapps-docs/developer/model-driven-apps/create-visualization-chart.md

@@ -34,7 +34,7 @@ To create a visualization programmatically, you must create a record for the [Sa
     > [!NOTE]
     >  Organization-owned visualizations can only be created by those users who have the System Administrator or System Customizer role.  
   
-- **Associated Table**: Visualizations are attached to tables. More information: [Tables supported for visualizations](view-data-with-visualizations-charts.md#SupportedVisualizationEntities). You can attach a chart to a supported table by using the [SavedQueryVisualization.PrimaryEntityTypeCode](../data-platform/reference/entities/savedqueryvisualization.md#BKMK_PrimaryEntityTypeCode) or [UserQueryVisualization.PrimaryEntityTypeCode](../data-platform/reference/entities/userqueryvisualization.md#BKMK_PrimaryEntityTypeCode) parameter.  
+- **Associated Table**: Visualizations are attached to tables. More information: [Tables supported for visualizations](view-data-with-visualizations-charts.md). You can attach a chart to a supported table by using the [SavedQueryVisualization.PrimaryEntityTypeCode](../data-platform/reference/entities/savedqueryvisualization.md#BKMK_PrimaryEntityTypeCode) or [UserQueryVisualization.PrimaryEntityTypeCode](../data-platform/reference/entities/userqueryvisualization.md#BKMK_PrimaryEntityTypeCode) parameter.  
 
 <a name="CreateChart"></a>   
 

powerapps-docs/developer/model-driven-apps/define-ribbon-display-rules.md

@@ -24,7 +24,7 @@ When configuring ribbon elements, you can define specific rules to control when
 - Use the /`RuleDefinitions`/DisplayRules/`<DisplayRule>` element to define rules controlling when the ribbon element should be displayed.  
 
 - Use the /CommandDefinitions/`CommandDefinition`/DisplayRules/`<DisplayRule>` element to associate specific display rules to a command definition.  
-- 
+
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
 ## Control when ribbon elements are displayed  

powerapps-docs/developer/model-driven-apps/define-ribbon-tab-display-rules.md

@@ -2,7 +2,7 @@
 title: "Define ribbon tab display rules (model-driven apps) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces"
 description: "Learn about defining ribbon tab displays rules." # 115-145 characters including spaces. This abstract displays in the search result."
 keywords: ""
-ms.date: 10/31/2018
+ms.date: 04/14/2021
 ms.service: powerapps
 ms.custom:
   - ""
@@ -21,23 +21,21 @@ search.app:
 
 # Define ribbon tab display rules
 
-<!-- https://docs.microsoft.com/dynamics365/customer-engagement/developer/customize-dev/define-ribbon-tab-display-rules -->
-
 Tab display rules control whether a specific tab is displayed for a ribbon or not.  
 
- Unlike other ribbon elements like groups or specific controls, you must explicitly provide a tab display rule for a tab to be displayed in the ribbon. By default, other ribbon elements will always display unless a display rule removes them.  
-  
- `<TabDisplayRule>` elements require that the `TabCommand` attribute matches a `<Tab>` `Command` attribute value.  
+Unlike other ribbon elements like groups or specific controls, you must explicitly provide a tab display rule for a tab to be displayed in the ribbon. By default, other ribbon elements will always display unless a display rule removes them.  
 
- In the `RibbonDiffXml`, tabs can be defined for specific entities or defined globally. 
- If the tab is defined for an entity, the only valid type of rule is `<EntityRule>`. 
- Because defining a tab in the scope of a particular entity already limits the tab to only that entity, the only valid attributes are `AppliesTo` (`PrimaryEntity` or `SelectedEntity`) and `Context` (`Form`, `HomePageGrid`, `SubGridStandard`, or `SubGridAssociated`).  
+ `<TabDisplayRule>` elements require that the `TabCommand` parameter matches a `<Tab>` `Command` value.  
 
- When you define a tab display rule globally in the `RibbonDiffXml` for the application ribbons, you can apply both `EntityRule` elements and `<PageRule>` elements.  
+In the `RibbonDiffXml`, tabs can be defined for specific tables or defined globally. If the tab is defined for a table, the only valid type of rule is `<EntityRule>`. Because defining a tab in the scope of a particular table already limits the tab to only that table, the only valid parameters are `AppliesTo` (`PrimaryEntity` or `SelectedEntity`) and `Context` (`Form`, `HomePageGrid`, `SubGridStandard`, or `SubGridAssociated`).  
+
+[!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
+
+When you define a tab display rule globally in the `RibbonDiffXml` for the application ribbons, you can apply both `EntityRule` elements and `<PageRule>` elements.  
 
 ### See also  
  [Customize commands and the ribbon](customize-commands-ribbon.md)   
- [Define Scaling for Ribbon elements](define-scaling-ribbon-elements.md)   
- [Pass Parameters to a URL by using the Ribbon](pass-parameters-url-by-using-ribbon.md)
+ [Define scaling for ribbon elements](define-scaling-ribbon-elements.md)   
+ [Pass parameters to a URL by using the ribbon](pass-parameters-url-by-using-ribbon.md)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]