Merge branches 'kabala-timeline-feature' and 'master' of https://github.com/MicrosoftDocs/powerapps-docs-pr into kabala-timeline-feature

Author: kabala123

.openpublishing.redirection.json

@@ -1,10 +1,15 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/common-data-service/fill-app-submission-form-appsource.md",
+      "redirect_url": "register-microsoft-partner-network",
+      "redirect_document_id": "false"
+    },    
     {
       "source_path": "powerapps-docs/maker/portals/configure/view-email-in-timeline.md",
       "redirect_url": "view-all-activities-in-portal-timeline",
       "redirect_document_id": "false"
-    },    
+    }, 
     {
       "source_path": "powerapps-docs/maker/canvas-apps/working-with-environments.md",
       "redirect_url": "/power-platform/admin/working-with-environments",

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

@@ -361,15 +361,13 @@
   - name: Publish your app on AppSource
     href: publish-app-appsource.md
     items:
-    - name: 'Step 1: Fill the app submission form on AppSource'
-      href: fill-app-submission-form-appsource.md
-    - name: 'Step 2: Register for Microsoft Partner Network account'
+    - name: 'Step 1: Create a Microsoft Partner Center account'
       href: register-microsoft-partner-network.md
-    - name: 'Step 3: Create a managed solution for your app'
+    - name: 'Step 2: Create a managed solution for your app'
       href: create-solution-app-appsource.md
-    - name: 'Step 4: Create an AppSource package for your app'
+    - name: 'Step 3: Create an AppSource package for your app'
       href: create-package-app-appsource.md
-    - name: 'Step 5: Store your AppSource Package on Azure Storage and generate a URL with SAS key'
+    - name: 'Step 4: Store your AppSource Package on Azure Storage and generate a URL with SAS key'
       href: store-appsource-package-azure-storage.md
     - name: 'Next steps: Submit your app on Partner Center'
       href: next-steps-submit-app-cloud-partner-portal.md

powerapps-docs/developer/common-data-service/create-package-app-appsource.md

@@ -1,21 +1,21 @@
 ---
-title: "Step 4: Create an AppSource package for your app (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+title: "Step 3: Create an AppSource package for your app (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about how to create an AppSource package (.zip file) to include your solution and demo data files along with other required files." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
 ms.date: 10/31/2018
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
-author: "shmcarth" # GitHub ID
-ms.author: "jdaly" # MSFT alias of Microsoft employees only
-manager: "ryjones" # MSFT alias of manager or PM counterpart
+author: "KumarVivek" # GitHub ID
+ms.author: "kvivek" # MSFT alias of Microsoft employees only
+manager: "annbe" # MSFT alias of manager or PM counterpart
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
 ---
-# Step 4: Create an AppSource package for your app
+# Step 3: Create an AppSource package for your app
 
 You must create an AppSource package (.zip file) to include your solution and demo data files along with other required files. An AppSource package consists of the following files:
 
@@ -136,4 +136,4 @@ The final step is to add all the components that you created earlier into a sing
 
 
 > [!div class="nextstepaction"]
-> [Step 5: Store your AppSource Package on Azure Storage](store-appsource-package-azure-storage.md) 
+> [Step 4: Store your AppSource Package on Azure Storage](store-appsource-package-azure-storage.md) 

powerapps-docs/developer/common-data-service/create-solution-app-appsource.md

@@ -1,21 +1,21 @@
 ---
-title: "Step 3: Create a managed solution for your app (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+title: "Step 2: Create a managed solution for your app (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about how to create a managed solution for your app to include all the components. This is required for publishing an app to Appsource." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 12/20/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
-author: "shmcarth" # GitHub ID
-ms.author: "jdaly" # MSFT alias of Microsoft employees only
-manager: "ryjones" # MSFT alias of manager or PM counterpart
+author: "KumarVivek" # GitHub ID
+ms.author: "kvivek" # MSFT alias of Microsoft employees only
+manager: "annbe" # MSFT alias of manager or PM counterpart
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
 ---
-# Step 3: Create a managed solution for your app
+# Step 2: Create a managed solution for your app
 
 Create a managed solution to include all the components for your app. You might find these topics helpful as you plan and create a managed solution to package your app components:
 - [Introduction to solutions](introduction-solutions.md)
@@ -48,5 +48,5 @@ You will have a solution file (example: *SampleSolution.zip*) and optionally a d
 
 
 > [!div class="nextstepaction"]
-> [Step 4: Create an AppSource package for your app](create-package-app-appsource.md) 
-  
+> [Step 3: Create an AppSource package for your app](create-package-app-appsource.md) 
+  

powerapps-docs/developer/common-data-service/fill-app-submission-form-appsource.md

@@ -0,0 +1,56 @@
+---
+title: " Assign chart to another user (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "This sample showcases how to assign a user-owned visualization to another user " # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 12/20/2019
+ms.reviewer: ""
+ms.service: powerapps
+ms.topic: "samples"
+author: "JimDaly" # GitHub ID
+ms.author: "jdaly" # MSFT alias of Microsoft employees only
+manager: "ryjones" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+
+# Assign a chart to another user
+
+This sample shows how to assign a user-owned visualization to another using the [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message. You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AssignChartToAnotherUser).
+
+This sample requires an additional user that isn't available in your system. Create the required user manually in **Office 365** in order to run the sample without any errors. For this sample create a user profile **as is** shown below. 
+
+**First Name**: Kevin<br/>
+**Last Name**: Cook<br/>
+**Security Role**: Sales Manager<br/>
+**UserName**: [email protected]<br/>
+
+## How to run this sample
+
+[!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
+
+## What this sample does
+
+The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId attribute of the record.
+
+## How this sample works
+
+In order to simulate the scenario described in [What this sample does](#what-this-sample-does), the sample will do the following:
+
+### Setup
+
+1. Checks for the current version of the org.
+2. The `CreateRequiredRecords` method creates a sample account and some opportunity records for the visualization.
+3. The `newUserOwnedVisualization` method creates the visualization entity instance.
+
+### Demonstrate
+
+1. The `AssignRequest` method assigns the visualization or chart to the newly created user.
+
+### Clean up
+
+1. Display an option to delete the sample data in [Setup](#setup).
+
+   The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.

powerapps-docs/developer/common-data-service/media/S2S-new-appuser1.png

@@ -0,0 +1,58 @@
+---
+title: " Assign dashboard to another user (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "This sample showcases how to assign a user-owned dashboard to another user " # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 12/20/2019
+ms.reviewer: ""
+ms.service: powerapps
+ms.topic: "samples"
+author: "JimDaly" # GitHub ID
+ms.author: "jdaly" # MSFT alias of Microsoft employees only
+manager: "ryjones" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+
+# Assign a user-owned dashboard to another user
+
+This sample shows how to assign a user-owned visualization to another using the [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message. Because you can’t delete a user-owned dashboard that is assigned to another user, this sample shows how to use impersonation to delete the user-owned dashboard. You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AssignUserOwnedDashboardToAnother).
+
+This sample requires an additional user that isn't available in your system. Create the required user manually in **Office 365** in order to run the sample without any errors. For this sample create a user profile **as is** shown below. 
+
+**First Name**: Kevin<br/>
+**Last Name**: Cook<br/>
+**Security Role**: Sales Manager<br/>
+**UserName**: [email protected]<br/>
+
+## How to run this sample
+
+[!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
+
+## What this sample does
+
+The [AssignRequest](https://docs.microsoft.com/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message is intended to be used in a scenario where it contains the data that is needed to assign the specified record to a new owner (user or team) by changing the OwnerId attribute of the record.
+
+## How this sample works
+
+In order to simulate the scenario described in [What this sample does](#what-this-sample-does), the sample will do the following:
+
+### Setup
+
+1. Checks for the current version of the org.
+2. The `CreateRequiredRecords` method creates entity records that this sample requires.
+3. The `mySavedQuery` method grabs the default public view for the opportunities.
+4. The `visualizationQuery` method retrieves the visualizations out of the system. This sample assumes that you have the **Top opportunities**. 
+5. The `_otherUSerId` method creates the user to whom the dashboard will be assigned.
+
+### Demonstrate
+
+1. The `AssignRequest` method assigns the visualization or chart to the newly created user.
+
+### Clean up
+
+1. Display an option to delete the sample data in [Setup](#setup).
+
+   The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.