Merging changes synced from https://github.com/MicrosoftDocs/powerapps-docs-pr (branch live)

Author: bishalgoswami

powerapps-docs/developer/common-data-service/activity-entities.md

@@ -1,6 +1,6 @@
 ---
 title: "Activity entities (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "In Dynamics 365 (online), activities are tasks that you or your teams perform when they contact customers, for example, sending letters or making telephone calls." # 115-145 characters including spaces. This abstract displays in the search result.
+description: "Activities are tasks that you or your teams perform when they contact customers, for example, sending letters or making telephone calls." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"

powerapps-docs/developer/common-data-service/apply-slas-entities.md

@@ -63,7 +63,7 @@ Service level agreements (SLAs) in Common Data Service help you define the level
 
 <a name="Limitations"></a>   
 
-## Limitations to applying SLAs in Dynamics 365 (online)  
+## Limitations to applying SLAs  
 
  In Common Data Service, the following limitations are applicable for SLAs per Common Data Service instance (organization):  
 

powerapps-docs/developer/common-data-service/connect-microsoft-office-365.md

@@ -1,6 +1,6 @@
 ---
 title: "Connect with Microsoft Office 365 and Common Data Service (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "The Microsoft Office 365 portal provides a single sign-on experience for Office 365 customers where they can sign in once and access any Office 365 application, including Dynamics 365 (online)" # 115-145 characters including spaces. This abstract displays in the search result.
+description: "The Microsoft Office 365 portal provides a single sign-on experience for Office 365 customers where they can sign in once and access any Office 365 application" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"
@@ -22,14 +22,14 @@ Common Data Service is part of the Office 365 collaboration and productivity too
  Using federation, applications can connect to Common Data Service using the same system user identities and credentials available in an Azure Active Directory based network. More information: [Single sign-on roadmap](https://technet.microsoft.com/library/hh967643.aspx).  
 
 ## In This Section  
- [Dynamics 365 (online) Integration with Office 365](online-integration-office-365.md)  
+ [Common Data Service Integration with Office 365](online-integration-office-365.md)  
 
- [Authenticate Office 365 Users with Dynamics 365 (online) Web Services](/dynamics365/customer-engagement/developer/authenticate-office-365-users-customer-engagement-web-services)  
+ [Authenticate Office 365 Users with Common Data Service Web Services](/dynamics365/customer-engagement/developer/authenticate-office-365-users-customer-engagement-web-services)  
 
- [Sample: Authenticate Users with Dynamics 365 Web Services](/dynamics365/customer-engagement/developer/sample-authenticate-users-web-services)  
+ [Sample: Authenticate Users with Common Data Service Web Services](/dynamics365/customer-engagement/developer/sample-authenticate-users-web-services)  
 
 ## Related Sections  
- [Authenticate Users with Dynamics 365 Web Services](/dynamics365/customer-engagement/developer/authenticate-users)  
+ [Authenticate Users with Common Data Service Web Services](/dynamics365/customer-engagement/developer/authenticate-users)  
 
- [Connect to the Dynamics 365 Web Services](/dynamics365/customer-engagement/developer/authenticate-office-365-users-customer-engagement-web-services)  
+ [Connect to the Common Data Service Web Services](/dynamics365/customer-engagement/developer/authenticate-office-365-users-customer-engagement-web-services)  
 

powerapps-docs/developer/common-data-service/customization-solutions-file-schema.md

@@ -8,8 +8,6 @@ ms.service: powerapps
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "article"
-applies_to: 
-  - "Dynamics 365 (online)"
 helpviewer_keywords: 
   - "schemas"
 ms.assetid: 71e3e594-0240-4af1-99b4-135042b7a000
@@ -23,7 +21,6 @@ search.app:
   - PowerApps
   - D365CE
 ---
-<!-- https://docs.microsoft.com/dynamics365/customer-engagement/developer/customize-dev/customization-solutions-file-schema -->
 
 # Customization solutions file schema
 

powerapps-docs/developer/common-data-service/isv-app-management.md

@@ -45,7 +45,7 @@ To access the public preview of ISV Studio, navigate your browser to [https://ak
 
 ## Pre-requisites
 
-1. The ISV must be associated with a Microsoft registered Partner organization [ISV] that has one or more supported apps published in [AppSource](https://appsource.microsoft.com/). Supported apps include Power Apps and model-driven apps in Dynamics 365 such as Dynamics 365 Sales and Dynamics 365 Customer Service.
+1. The ISV must be associated with a Microsoft registered Partner organization [ISV] that has one or more supported apps published in [AppSource](https://appsource.microsoft.com/). Supported apps include model-driven apps created using Power Apps and Dynamics 365 apps such as Dynamics 365 Sales and Dynamics 365 Customer Service.
 
 2. The ISV must have an [Azure Active Directory](https://azure.microsoft.com/services/active-directory/) (AAD) account and the account must be configured as an app contributor or owner in Partner Center for the particular ISV.
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/openForm.md

@@ -120,8 +120,7 @@ This function is passed an object as a parameter. The object has a <b>savedEntit
 <td>Function</td>
 <td>No</td>
 <td>A function to execute when the operation fails.<br>
-
-<b>NOTE</b>: On [Unified Interface](/dynamics365/customer-engagement/admin/about-unified-interface), the <b>errorCallback</b> function will be executed only if you are opening a quick create form.</td>
+</td>
 </tr>
 </table>
 

powerapps-docs/maker/common-data-service/api-limits-overview.md

@@ -17,7 +17,7 @@ search.app:
 ---
 # Common Data Service API limits overview
 
-Common Data Service API limits help ensure service levels, availability and quality. Common Data Service API limits are part of the Power Platform Request limits and allocations. This topic will introduce limits specifically for Common Data Service applicable for model-driven apps in Dynamics 365 (such as Dynamics 365 Sales and Dynamics 365 Customer Service), Power Apps, and Power Automate connecting to Common Data Service/model-driven apps in Dynamics 365. 
+Common Data Service API limits help ensure service levels, availability and quality. Common Data Service API limits are part of the Power Platform Request limits and allocations. This topic will introduce limits specifically for Common Data Service applicable for Power Apps, Power Automate, and customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation) connecting to Common Data Service. 
 
 For information about limits for all areas within Power Platform, see [Power Platform Request limits and allocations](/power-platform/admin/api-request-limits-allocations).
 

powerapps-docs/maker/common-data-service/data-platform-restricted-entities.md

@@ -4,7 +4,7 @@ description: A list of restricted entities in Common Data Service that require D
 author: KumarVivek
 ms.service: powerapps
 ms.topic: reference
-ms.date: 04/15/2020
+ms.date: 08/25/2020
 ms.author: kvivek
 search.audienceType: 
   - maker
@@ -15,29 +15,27 @@ search.app:
 
 # Restricted entities requiring Dynamics 365 licenses
 
-> [!IMPORTANT]
-> This topic is out-of-date and will be updated soon to reflect the latest licensing changes that are applicable starting October 1, 2019. For the latest information on licensing requirements for entities, see the [Power Apps licensing guide](https://go.microsoft.com/fwlink/p/?linkid=2085130).
+App makers, who are building custom apps, can use all of the Common Data Service entities available within [Common Data Model](https://docs.microsoft.com/common-data-model/) to create apps and flows for users who have any version of Power Apps license.  
 
-App makers can use most of the entities available within Common Data Service to create apps and flows for users who have only a Power Apps Plan 1 license. However, some entities contain complex business logic that requires app users to have a Power Apps Plan 2 or Power Automate Plan 2 license (for more information, see [Entity license requirements](data-platform-entity-licenses.md)). An even smaller set of entities tied to Dynamics 365 products requires canvas and model-driven app users to have a license for the corresponding Dynamics 365 product if they need to create, update, or delete records within the entities. These are referred to as *restricted* entities.
+However, a smaller set of entities tied to Dynamics 365 products require canvas and model-driven app users to have a license for the corresponding Dynamics 365 product if they need to create, update, or delete records within the entities. These are referred to as restricted entities.
 
 Entities may be restricted to a Dynamics 365 license for the following reasons:
-
-* The entity is used to store and maintain product-specific configuration data that is typically not used outside of the application.
+* The entity is used to store and maintain product-specific configuration data that should typically be not used outside of the application.
 * The entity is accompanied by advanced logic that creates and maintains data in a specific way when used within a Dynamics 365 product.
 
-If an app or flow only reads information from an entity, a Dynamics 365 license is not required and an appropriate Power Apps or Power Automate license is all that's needed. 
+If an app or flow only reads information from an entity, a Dynamics 365 license is not required and an appropriate Power Apps or Power Automate license is all that's needed.
 
 ## Restricted entities for create, update, and delete operations
-The following table lists the restricted entities and the associated Dynamics 365 licensing requirements for Power Apps and Power Automate app users who create, update, or delete data stored within the entities. 
+The following table lists the restricted entities and the associated Dynamics 365 license requirements for users who create, update, or delete data stored within these entities. 
 
 |Entity  |Logical name  |License required  |
 |---------|---------|---------|
 Actual |msdyn_actual |Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Agreement Business Process |msdyn_bpf_baa0a411a239410cb8bded8b5fdd88e3 |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Booking journal | msdyn_bookingjournal|Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Booking Setup Metadata | msdyn_bookingsetupmetadata|Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
-Booking timestamp | msdyn_bookingtimestamp|Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
-Case | incident | Dynamics 365 for Customer Service, Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
+Booking timestamp | msdyn_bookingtimestamp|Dynamics 365 for Field Service<br> **or** Dynamics 365 Customer Engagement plan<br> **or** Dynamics 365 plan
+Case<sup>1</sup> | incident | Dynamics 365 for Customer Service Professional edition <br>**or** Dynamics 365 for Customer Service Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Case to Work Order Business Process |msdyn_bpf_989e9b1857e24af18787d5143b67523b |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Configuration |msdyn_configuration |Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Entitlement | entitlement | Dynamics 365 for Customer Service, Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
@@ -65,7 +63,7 @@ Resource Restriction (Deprecated) |msdyn_workorderresourcerestriction | Dynamics
 Routing rule set | routingrule | Dynamics 365 for Customer Service, Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Schedule Board Setting |msdyn_scheduleboardsetting |Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Scheduling Parameter |msdyn_schedulingparameter |Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
-SLA| sla | Dynamics 365 for Customer Service, Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
+SLA| sla | Dynamics 365 for Customer Service Professional edition <br>**or** Dynamics 365 for Customer Service Enterprise edition <br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 System User Scheduler Setting |msdyn_systemuserschedulersetting|Dynamics 365 for Field Service <br> **or** Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Transaction Connection|msdyn_transactionconnection |Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Transaction Origin|msdyn_transactionorigin |Dynamics 365 for Project Service Automation<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
@@ -74,6 +72,12 @@ Unique Number|msdyn_uniquenumber |Dynamics 365 for Field Service<br>**or** Dynam
 Work Order Business Process |msdyn_bpf_d3d97bac8c294105840e99e37a9d1c39 |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 Work Order Details Generation Queue (Deprecated)|msdyn_workorderdetailsgenerationqueue |Dynamics 365 for Field Service<br>**or** Dynamics 365 Customer Engagement plan <br> **or** Dynamics 365 plan
 
+[1] *Case Entity actions permitted with only Power Apps license:*  
+     Power Apps licensed users can ‘create’ cases; can ‘read’, ‘update’ and ‘delete’ self-created cases to enable scenarios including employee self-service and case creation on        behalf of customers. Power Apps licensed users can only perform ‘read’ operation on cases created by other users. They cannot ‘update’, ‘resolve’, ‘route’,     ‘close’,‘delete’,‘assign’,‘duplicate’ , ‘merge’ , ‘create child cases’ or perform any other custom operation on cases created by others- Users can't act as a customer service agent, can't manage cases.
+
+> [!NOTE]
+> Dynamics 365 Customer Engagement Plan and Dynamics 365 Plan licenses are no longer available for purchase and is referenced here only for the benefit of existing customers who have bought these licenses in the past.
+
 ## Licensing
 For more information on Power Apps and Dynamics 365 licenses, see [Licensing overview](../../administrator/pricing-billing-skus.md) page.
 

powerapps-docs/maker/model-driven-apps/add-move-or-delete-sections-on-form.md

@@ -1,16 +1,10 @@
 ---
 title: "Add, configure, move, or delete sections on a form using the form designer | MicrosoftDocs"
 ms.custom: ""
-ms.date: 08/26/2019
+ms.date: 08/25/2020
 ms.reviewer: ""
 ms.service: powerapps
-ms.suite: ""
-ms.tgt_pltfrm: ""
 ms.topic: "get-started-article"
-applies_to: 
-  - "Dynamics 365 (online)"
-  - "Dynamics 365 Version 9.x"
-  - "PowerApps"
 author: "Aneesmsft"
 ms.author: "matp"
 manager: "kvivek"
@@ -72,6 +66,9 @@ These are the properties available to configure a section when you create or edi
 |**Display options** | **Hide on phone** |  The section can be hidden to render a condensed version of this form on phone screens. |
 |**Formatting** |  **Columns** |  Specify up to four columns for the section. |
 
+> [!Important]
+> Sections that don't have any fields or controls will be hidden at runtime in Unified Interface.
+    
 ## Move sections on a form
 You can move sections using drag and drop or cut and paste actions. 
 

powerapps-docs/maker/model-driven-apps/configure-bing-maps-legacy.md

@@ -23,7 +23,7 @@ search.app:
   - D365CE
 ---
 # Configure a map on a form
-By default, the Bing maps control is configured on the main form for both the account and contact entities, which provides the ability to display a map on entity records. Although not configured by default, the Bing maps control can be added to the system user entity. The Bing maps control can also be used with some entities included with model-driven apps in Dynamics 365, such as Dynamics 365 Sales and Dynamics 365 Customer Service. For example, the lead, quote, order, invoice, and competitor entities. The Bing maps control can't be used with custom entities.  
+By default, the Bing maps control is configured on the main form for both the account and contact entities, which provides the ability to display a map on entity records. Although not configured by default, the Bing maps control can be added to the system user entity. The Bing maps control can also be used with some entities included with Dynamics 365 apps, such as Dynamics 365 Sales and Dynamics 365 Customer Service. For example, the lead, quote, order, invoice, and competitor entities. The Bing maps control can't be used with custom entities.  
 
 When enabled, the map displays the ___location specified in the address composite fields for the given record.