Merge branch 'master' into portals-1805092

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -1854,12 +1854,7 @@
       "source_path": "powerapps-docs/maker/maker/canvas-apps/webinars-listing.md",
       "redirect_url": "https://powerusers.microsoft.com/t5/Samples-Learning-and-Videos/ct-p/PA_Comm_Galleries",
       "redirect_document_id": "false"
-    },
-    {
-      "source_path": "powerapps-docs/developer/common-data-service/index.md",
-      "redirect_url": "/powerapps/developer/common-data-service/overview",
-      "redirect_document_id": "false"
-    },
+    },    
     {
       "source_path": "powerapps-docs/developer/common-data-service/org-service/index.md",
       "redirect_url": "/powerapps/developer/common-data-service/org-service/overview",
@@ -1900,11 +1895,6 @@
       "redirect_url": "/powerapps/developer/common-data-service/index",
       "redirect_document_id": "false"
     },
-    {
-      "source_path": "powerapps-docs/developer/model-driven-apps/index.md",
-      "redirect_url": "/powerapps/developer/model-driven-apps/overview",
-      "redirect_document_id": "false"
-    },
     {
       "source_path": "powerapps-docs/maker/canvas-apps/working-with-experimental.md",
       "redirect_url": "working-with-experimental-preview",
@@ -1913,17 +1903,12 @@
     {
       "source_path": "powerapps-docs/maker/common-data-service/entity-relationship-behavior.md",
       "redirect_url": "create-edit-entity-relationships#entity-relationship-behavior",
-      "redirect_document_id": "false"
-    },
-    {
-      "source_path": "powerapps-docs/maker/common-data-service/index.md",
-      "redirect_url": "/powerapps/maker/common-data-service/data-platform-intro",
-      "redirect_document_id": "false"
+      "redirect_document_id": false
     },
     {
-      "source_path": "powerapps-docs/maker/model-driven-apps/index.md",
-      "redirect_url": "/powerapps/maker/model-driven-apps/model-driven-app-overview",
-      "redirect_document_id": "false"
+      "source_path": "powerapps-docs/maker/canvas-apps/embed-teams-app.md",
+      "redirect_url": "/powerapps/teams/embed-teams-app",
+      "redirect_document_id": false
     }
   ]
 }

clear_filter.png

@@ -0,0 +1,29 @@
+---
+title: "View charts on a form page in model-driven apps| MicrosoftDocs"
+description: Use interative dashboards to filter data in Power Apps
+author: mduelae
+manager: kvivek
+ms.service: powerapps
+ms.component: pa-user
+ms.topic: conceptual
+ms.date: 9/2/2020
+ms.author: mduelae
+ms.custom: ""
+ms.reviewer: ""
+ms.assetid: 
+search.audienceType: 
+  - enduser
+search.app: 
+  - PowerApps
+  - D365CE
+---
+# View charts on a form page
+
+Use interactive dashboards to see workload information and take action. The charts on a interactive dashboard serves as a simple filtering source. You can select different data points on a chart to filter data based on the filter criteria. 
+Interactive dashboards are system dashboards that only an admin can create. To learn more on how to create and configure interactive dashboards, see [Create and configure model-driven app interactive experience dashboards](https://docs.microsoft.com/powerapps/maker/model-driven-apps/configure-interactive-experience-dashboards).
+
+Interactive dashboards come in two forms: multi-stream and single-stream. In addition, multi-stream dashboards can be home page or entity-specific dashboards. The multi-stream dashboards display data in real time over multiple data streams. 
+
+
+> [!div class="mx-imgBorder"]
+> ![Multi-stream interactive dashboard](media/interactive_dashboard.png "Multi-stream interactive dashboard") 

powerapps-docs/chart_on_form.md

@@ -1,6 +1,6 @@
-- name: Common Data Service
-  href: ../../maker/common-data-service/data-platform-intro.md
-- name: Developer overview
+- name: Common Data Service developer guide
+  href: index.yml
+- name: Overview
   href: overview.md
 - name: Get started
   href: get-started-cds-developers.md

powerapps-docs/developer/common-data-service/TOC.yml

@@ -333,7 +333,7 @@ If your application is currently using the low-level <xref:Microsoft.Xrm.Sdk.Cli
 
 More information:
 
-- [Build Windows client applications using the XRM tools](/xrm-tooling/build-windows-client-applications-xrm-tools).
+- [Build Windows client applications using the XRM tools](xrm-tooling/build-windows-client-applications-xrm-tools.md).
 - [Deprecation of Office365 authentication type and OrganizationServiceProxy class for connecting to Common Data Service](/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-common-data-service)
 
 ### Use Task Parallel Library with CrmServiceClient

powerapps-docs/developer/common-data-service/api-limits.md

@@ -32,7 +32,7 @@ The sequential segment is generated by SQL and hence uniqueness is guaranteed by
 > [!NOTE]
 >You can modify an existing format text attribute to be an auto-number format.
 
-When you add the auto-number attribute as a field to a form, the auto-number attribute field behaves as read-only in the form, and end-users cannot edit the field. The value is set only after you save the entity. You can see auto-number attribute as any other field value in views, grids and so on.
+In the legacy web client, when adding a control on a form bound to an auto-number attribute, the control is disabled automatically and behaves as read-only in the form where end-users cannot edit the control. In the Unified Interface, controls bound to an auto-number attribute need to explicitly be set as disabled. If you do not set the initial attribute value on the form, the value is set only after you save the entity. Auto-numbering can be applied to attribute field values in views, grids and so on.
 
 ### Examples
 The following examples show how to create a new auto-number attribute named **new\_SerialNumber** for a custom entity named **new\_Widget** which will have a value that looks like this: **WID-00001-AB7LSFG-20170913070240**.

powerapps-docs/developer/common-data-service/create-auto-number-attributes.md

@@ -0,0 +1,163 @@
+### YamlMime:Landing
+
+title: Common Data Service developer documentation
+summary: Learn how to write applications and web pages that can access Common Data Service business data, extend the functionality of the platform through plug-ins and workflow, or interface your business data to external systems.
+
+metadata:
+  title: Common Data Service developer documentation
+  description: Provides access to highlighted areas within the Common Data Service developer documentation
+  services: service
+  ms.service: powerapps 
+  ms.subservice: subservice
+  ms.topic: landing-page 
+  ms.collection: collection
+  author: phecke
+  ms.author: pehecke
+  ms.date: 09/08/2020 
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
+
+landingContent:
+
+  # Card 
+  - title: Get started
+    linkLists:
+       - linkListType: overview
+         links:
+          - text: Developer overview
+            url: overview.md
+          - text: "Developers: Get started"
+            url: get-started-CDS-developers.md
+       - linkListType: learn
+         links:
+          - text: Introduction to Common Data Service for developers
+            url: https://docs.microsoft.com/learn/modules/intro-cds-developers-power-platform/
+         
+          
+  # Card
+  - title: Work with data
+    linkLists:
+       - linkListType: overview
+         links:
+          - text: Work with data using code
+            url: work-with-data-cds.md
+          - text: Types and operations (Web API)
+            url: /powerapps/developer/common-data-service/webapi/web-api-types-operations
+          - text: Entity operations (Organization service)
+            url: /powerapps/developer/common-data-service/org-service/entity-operations
+          - text: Use FetchXML to query data
+            url: /powerapps/developer/common-data-service/use-fetchxml-construct-query
+          - text: Use SQL to query data
+            url: /powerapps/developer/common-data-service/cds-sql-query
+
+  # Card
+  - title: Integrate external data
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: Azure integration
+            url: /powerapps/developer/common-data-service/azure-integration
+          - text: Webhooks
+            url: /powerapps/developer/common-data-service/use-webhooks
+          - text: Synchronize data with external system
+            url: /powerapps/developer/common-data-service/data-synchronization
+          - text: Import data
+            url: /powerapps/developer/common-data-service/import-data
+          - text: Data Export Service
+            url: /powerapps/developer/common-data-service/data-export-service
+      
+
+  # Card
+  - title: Apply business logic
+    linkLists:
+      - linkListType: concept
+        links:
+          - text: Event framework
+            url: /powerapps/developer/common-data-service/event-framework
+      - linkListType: overview
+        links:
+          - text: Plug-ins
+            url: /powerapps/developer/common-data-service/plug-ins
+          - text: Workflow extensions
+            url: /powerapps/developer/common-data-service/workflow/workflow-extensions
+      - linkListType: tutorial
+        links:
+          - text: Write and register a plug-in
+            url: /powerapps/developer/common-data-service/tutorial-write-plug-in
+  
+  # Card
+  - title: Deploy and publish
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: Solution concepts
+            url: /powerapps/developer/common-data-service/introduction-solutions
+          - text: ALM for developers
+            url: https://docs.microsoft.com/power-platform/alm/alm-for-developers
+      - linkListType: sample
+        links:
+          - text: Work with solutions using the SDK APIs
+            url: /power-platform/alm/solution-api
+      - linkListType: how-to-guide
+        links:
+          - text: Publish your app on AppSource
+            url: /powerapps/developer/common-data-service/publish-app-appsource          
+
+    # Card
+  - title: Create client applications
+    linkLists: 
+       - linkListType: overview
+         links:
+          - text: Authentication and the web services
+            url: authentication.md
+          - text: Build web applications using Server-to-Server (S2S) authentication
+            url: build-web-applications-server-server-s2s-authentication.md
+          - text: Use OAuth with CORS to connect an SPA
+            url: /powerapps/developer/common-data-service/oauth-cross-origin-resource-sharing-connect-single-page-application
+          - text: Build Windows client applications using the XRM tools
+            url: xrm-tooling/build-windows-client-applications-xrm-tools.md
+       - linkListType: tutorial
+         links:  
+          - text: Register an app with Azure Active Directory
+            url: walkthrough-register-app-azure-active-directory.md
+
+  # Card
+  - title: Tools and resources
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: View the developer resources page
+            url: /powerapps/developer/common-data-service/view-download-developer-resources
+          - text: Developer tools
+            url: /powerapps/developer/common-data-service/developer-tools
+          - text: Microsoft Power Apps CLI
+            url: /powerapps/developer/common-data-service/powerapps-cli
+          - text: Community tools
+            url: /powerapps/developer/common-data-service/community-tools
+  
+  # Card
+  - title: Entity and API reference
+    linkLists:
+      - linkListType: reference
+        links:
+          - text: Entity reference
+            url: reference/about-entity-reference.md
+          - text: SDK API class libraries
+            url: https://docs.microsoft.com/dotnet/api/?view=dynamics-general-ce-9
+          - text: Web API
+            url: /dynamics365/customer-engagement/web-api/about?view=dynamics-ce-odata-9
+          - text: XRM Tooling API Reference
+            url: https://docs.microsoft.com/dotnet/api/?view=dynamics-xrmtooling-ce-9 
+
+
+  # Card
+  - title: Related resources
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: Canvas apps Developer Guide
+            url: ../../maker/canvas-apps/dev-enterprise-intro.md
+          - text: Model-driven apps Developer Guide
+            url: ../model-driven-apps/index.yml
+          - text: Power Apps component framework
+            url: ../component-framework/overview.md    

powerapps-docs/developer/common-data-service/index.yml

@@ -17,14 +17,16 @@ search.app:
 ---
 # Use ExecuteAsync to execute messages asynchronously
 
-Except for two, all data operations using the SDK assembly request classes are synchronous.
+Except for three, all data operations using the SDK assembly request classes are synchronous.
 
 Importing a solution is one operation which can require considerable resources, so there is an option to execute this operation asynchronously using the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class. The <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> request class performs similar resource intensive operations.
 
 Importing a solution asynchronously improves system performance by postponing message execution until some later time when the server load may be less. Interactive users do not have to wait for the target message to execute before they can continue. This is especially useful when importing solutions which may take a few minutes or more to execute.  
+
+Merging records with a large number of related activities or other entity types can also take a long time to update all the related records, so executing these in the background can improve the user experience.
 
 > [!NOTE]
->  <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest> and <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> are the only request classes that can be used with the `ExecuteAsync` message.
+>  <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest>, <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest>, and <xref:Microsoft.Crm.Sdk.Messages.MergeRequest> are the only request classes that can be used with <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest>.
   
 Use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class to execute a message asynchronously. You configure the request and pass the request instance as an argument to <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*>. <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncResponse> returns with the ID of the asynchronous job. You can (optionally) query the job using the ID to find out its current state.  
 
@@ -64,4 +66,4 @@ You can then poll the [AsyncOperation](../reference/entities/asyncoperation.md)
 [Execute multiple requests using the Organization service](execute-multiple-requests.md)
 
 
-  
+  

powerapps-docs/developer/common-data-service/org-service/use-executeAsync.md

@@ -2,13 +2,13 @@
 title: "Use messages with the Organization service (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Understand how messages are used to invoke operations using the organization service." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 09/11/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
 author: "JimDaly" # GitHub ID
-ms.author: "jdaly" # MSFT alias of Microsoft employees only
-manager: "ryjones" # MSFT alias of manager or PM counterpart
+ms.author: "pehecke" # MSFT alias of Microsoft employees only
+manager: "sunilg" # MSFT alias of manager or PM counterpart
 search.audienceType: 
   - developer
 search.app: 
@@ -87,7 +87,8 @@ You can pass optional parameters in messages using the <xref:Microsoft.Xrm.Sdk.O
 |Parameter|Description|Messages|  
 |-----------------|-----------------|--------------|  
 |`SolutionUniqueName`|A `String` that specifies the unique name of the solution to which the operation applies. More information: [Dependency tracking for solution components](../dependency-tracking-solution-components.md).|<xref:Microsoft.Crm.Sdk.Messages.AddPrivilegesRoleRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.DeleteRequest> <br /> <xref:Microsoft.Crm.Sdk.Messages.MakeAvailableToOrganizationTemplateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  
-|`SuppressDuplicateDetection`|A `Boolean` used to disable duplicate detection on a create or update operation. More information: [Use SuppressDuplicateDetection parameter to throw errors when you create or update record](detect-duplicate-data.md#use-suppressduplicatedetection-parameter-to-throw-errors-when-you-create-or-update-record) .|<xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  
+|`SuppressDuplicateDetection`|A `Boolean` used to disable duplicate detection on a create or update operation. More information: [Use SuppressDuplicateDetection parameter to throw errors when you create or update record](detect-duplicate-data.md#use-suppressduplicatedetection-parameter-to-throw-errors-when-you-create-or-update-record) .|<xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|
+|`tag`|A value to include within the `ExecutionContext` `SharedVariables` collection. |Any message that can have a plug-in step registered. More information: [Add a Shared Variable from the Organization Service](#add-a-shared-variable-from-the-organization-service)|
 
  The following sample shows how to pass an optional parameter:  
 
@@ -100,6 +101,32 @@ req["SuppressDuplicateDetection"] = true;
 CreateResponse response = (CreateResponse)svc.Execute(req);  
 ```  
 
+### Add a Shared Variable from the Organization Service
+
+You can set a string value that will be available to plug-ins within the ExecutionContext in the `SharedVariables` collection. More information: [Shared variables](../understand-the-data-context.md#shared-variables)
+
+```csharp
+var account = new Entity("account");
+account["name"] = "Contoso";
+
+var request = new CreateRequest() { Target = account };
+request["tag"] = "This is a value passed.";
+
+var response = (CreateResponse)svc.Execute(request);
+```
+
+
+Will result in the following value within the `SharedVariables` collection when sent using a webhook.
+
+```json
+{
+"key": "tag",
+"value": "This is a value passed."
+}
+```
+
+This can also be done using the Web API: [Add a Shared Variable from the Web API](../webapi/compose-http-requests-handle-errors.md#add-a-shared-variable-from-the-web-api)
+
 ### See also
 
 [Entity Operations using the Organization service](entity-operations.md)<br />