Merge branch 'main' into jdaly-main-open-app-url

Author: JimDaly

.openpublishing.redirection.json

@@ -1,5 +1,30 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/data-platform/outlook-client/sample-create-retrieve-outlook-filters.md",
+      "redirect_url": "../data-platform/org-service/samples/create-retrieve-outlook-filters",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/org-service/samples/install-remove-sample-data.md",
+      "redirect_url": "../data-platform/sample-data",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/org-service/samples/work-with-discovery-service.md",
+      "redirect_url": "../data-platform/org-service/samples/access-discovery-service",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/org-service/create-client-app.md",
+      "redirect_url": "../data-platform/connect-dataverse",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/on-premises-options.md",
+      "redirect_url": "../data-platform",
+      "redirect_document_id": "false"
+    },
     {
       "source_path": "powerapps-docs/developer/data-platform/customapi-table-columns.md",
       "redirect_url": "custom-api-tables#custom-api-table-columns",
@@ -707,17 +732,17 @@
     },
     {
       "source_path": "powerapps-docs/admin-view-user-licenses.md",
-      "redirect_url": "/powerapps/administrator/admin-view-user-licenses",
+      "redirect_url": "/power-platform/admin/admin-view-user-licenses",
       "redirect_document_id": "false"
     },
     {
       "source_path": "powerapps-docs/app-analytics.md",
-      "redirect_url": "/powerapps/administrator/index",
+      "redirect_url": "/power-platform/admin/analytics-powerapps",
       "redirect_document_id": "false"
     },
     {
       "source_path": "powerapps-docs/create-database.md",
-      "redirect_url": "/powerapps/administrator/create-database",
+      "redirect_url": "/power-platform/admin/create-database",
       "redirect_document_id": "false"
     },
     {

powerapps-docs/breadcrumb/toc.yml

@@ -7,46 +7,46 @@
     topichref: /power-platform/
     items:
     - name: Power Apps
-      tocHref: /powerapps/
-      topicHref: /powerapps/
+      tocHref: /power-apps/
+      topicHref: /power-apps/
       items:
       # Adding Create app for each type of app
       - name: Create apps
-        tocHref: /powerapps/maker/data-platform/
-        topicHref: /powerapps/maker/index
+        tocHref: /power-apps/maker/data-platform/
+        topicHref: /power-apps/maker/index
       - name: Create apps
-        tocHref: /powerapps/maker/model-driven-apps/
-        topicHref: /powerapps/maker/index     
+        tocHref: /power-apps/maker/model-driven-apps/
+        topicHref: /power-apps/maker/index     
       - name: Create apps
-        tocHref: /powerapps/maker/canvas-apps/
-        topicHref: /powerapps/maker/index       
+        tocHref: /power-apps/maker/canvas-apps/
+        topicHref: /power-apps/maker/index       
       #  Make sure Create apps appears for topics in developer folder 
       - name: Create apps
-        tocHref: /powerapps/developer/data-platform/
-        topicHref: /powerapps/maker/index
+        tocHref: /power-apps/developer/data-platform/
+        topicHref: /power-apps/maker/index
         items: 
         - name: Microsoft Dataverse
-          tocHref: /powerapps/developer/data-platform/
-          topicHref: /powerapps/maker/data-platform/index          
+          tocHref: /power-apps/developer/data-platform/
+          topicHref: /power-apps/maker/data-platform/index          
           items:
           - name: Developer
-            tocHref: /powerapps/developer/data-platform/
-            topicHref: /powerapps/developer/data-platform/index
+            tocHref: /power-apps/developer/data-platform/
+            topicHref: /power-apps/developer/data-platform/index
             items:
             - name: Organization Service
-              tocHref: /powerapps/developer/data-platform/org-service/
-              topicHref: /powerapps/developer/data-platform/org-service/index
+              tocHref: /power-apps/developer/data-platform/org-service/
+              topicHref: /power-apps/developer/data-platform/org-service/index
             - name: Web API
-              tocHref: /powerapps/developer/data-platform/webapi/
-              topicHref: /powerapps/developer/data-platform/webapi/index
+              tocHref: /power-apps/developer/data-platform/webapi/
+              topicHref: /power-apps/developer/data-platform/webapi/index
       - name: Create apps
-        tocHref: /powerapps/developer/model-driven-apps/
-        topicHref: /powerapps/maker/index
+        tocHref: /power-apps/developer/model-driven-apps/
+        topicHref: /power-apps/maker/index
         items:
         - name: Model-driven apps
-          tocHref: /powerapps/developer/model-driven-apps/
-          topicHref: /powerapps/maker/model-driven-apps/index      
+          tocHref: /power-apps/developer/model-driven-apps/
+          topicHref: /power-apps/maker/model-driven-apps/index      
           items:
           - name: Developer
-            tocHref: /powerapps/developer/model-driven-apps/
-            topicHref: /powerapps/developer/model-driven-apps/index    
+            tocHref: /power-apps/developer/model-driven-apps/
+            topicHref: /power-apps/developer/model-driven-apps/index    

powerapps-docs/developer/component-framework/code-components-alm.md

@@ -290,7 +290,7 @@ It's recommended that the MAJOR and MINOR version of the code component's versio
 
 A [Dataverse solution has four parts](/powerapps/maker/data-platform/update-solutions#understanding-version-numbers-for-updates) and it can be thought of in the following structure: `MAJOR.MINOR.BUILD.REVISION`.
 
-If you're using **AzureDevOps**, you can set your build pipeline versioning using the `Build` and `Rev` environment variables ([Run (build) number - Azure Pipelines](/azure/devops/pipelines/process/run-number?view=azure-devops&tabs=yaml&preserve-view=true)), and use PowerShell script similar to the approach described in the article [Use PowerShell scripts to customize pipelines](/azure/devops/pipelines/scripts/powershell?view=azure-devops&tabs=yaml#example-powershell-script-version-assemblies&preserve-view=true).
+If you're using **AzureDevOps**, you can set your build pipeline versioning using the `Build` and `Rev` environment variables ([Run (build) number - Azure Pipelines](/azure/devops/pipelines/process/run-number)), and use PowerShell script similar to the approach described in the article [Use PowerShell scripts to customize pipelines](/azure/devops/pipelines/scripts/powershell#example-powershell-script-version-assemblies).
 
 | Semantic version part | ControlManifest.Input.xml version part<br />`MAJOR.MINOR.PATCH` | Solution.xml version part<br />`MAJOR.MINOR.BUILD.REVISION` | AzureDevOps Build Version                                                                        |
 | --------------------- | --------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |

powerapps-docs/developer/component-framework/overview.md

@@ -2,16 +2,18 @@
 title: "Power Apps component framework overview in Microsoft Dataverse(contains video) | Microsoft Docs"
 description: "Use the Power Apps component framework to create code components to provide an enhanced experiences for people to view and work with data in forms, views, and dashboards."
 keywords: "Component Framework, code components, Power Apps controls"
-ms.author: jdaly
+ms.author: noazarur
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 04/01/2022
 ms.reviewer: jdaly
 ms.custom:
   - "dyn365-a11y"
   - "dyn365-developer"
 ms.topic: overview
 ms.subservice: pcf
+contributors: 
+  - JimDaly
 ---
 
 # Power Apps component framework overview

powerapps-docs/developer/data-platform/appendix-add-license-information-to-your-solution.md

@@ -1,20 +1,21 @@
 ---
 title: "Appendix: Add licensing information to your solution | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This article outlines the required steps to take license service IDs created in Partner Center and add them to the table definitions of your Dataverse solution." # 115-145 characters including spaces. This abstract displays in the search result.
-ms.custom: ""
-ms.date: 04/30/2021
-ms.reviewer: "pehecke"
-
+ms.date: 04/01/2022
+author: mikkelsen2000
+ms.author: pemikkel
+ms.reviewer: pehecke
+manager: jstrauss
 ms.topic: "article"
-author: "nkrb" 
 ms.subservice: dataverse-developer
-ms.author: "nabuthuk" 
-manager: "kvivek" 
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
+contributors: 
+  - JimDaly
+
 ---
 
 # Appendix: Add licensing information to your solution

powerapps-docs/developer/data-platform/application-insights-ilogger.md

@@ -1,20 +1,21 @@
 ---
 title: "Write Telemetry to your Application Insights resource using ILogger (preview)(Microsoft Dataverse) | Microsoft Docs"
 description: "When you enable Application Insights for your organization, any plug-ins written using the ILogger Interface provided in the SDK will write telemetry to your Application Insights resource."
-ms.custom: ""
-ms.date: 06/28/2021
-ms.reviewer: "pehecke"
-
+ms.date: 04/03/2022
+author: divka78
+ms.author: dikamath
+manager: sunilg
+ms.reviewer: pehecke
 ms.topic: "article"
-author: JimDaly
 ms.subservice: dataverse-developer
-ms.author: pehecke
-manager: kvivek
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
+contributors:
+ - JimDaly
+ - phecke
 ---
 
 # Write Telemetry to your Application Insights resource using ILogger (Preview)

powerapps-docs/developer/data-platform/apply-business-logic-with-code.md

@@ -1,24 +1,21 @@
 ---
 title: Apply business logic using code (Microsoft Dataverse)| Microsoft Docs
 description: Learn how to write code to customize business data processing in Microsoft Dataverse.
-services: ''
+ms.date: 04/03/2022
+author: divka78
+ms.author: dikamath
+manager: sunilg
+ms.reviewer: pehecke
 suite: powerapps
-documentationcenter: na
-author: JimDaly
-manager: kvivek
-
-ms.devlang: na
-ms.topic: article
-ms.tgt_pltfrm: na
-ms.workload: na
-ms.date: 03/12/2021
 ms.subservice: dataverse-developer
-ms.author: jdaly
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
+contributors:
+ - JimDaly
+ - phecke
 ---
 
 # Apply business logic using code

powerapps-docs/developer/data-platform/apply-slas-entities.md

@@ -5,7 +5,7 @@ ms.custom: ""
 ms.date: 07/19/2021
 ms.reviewer: "pehecke"
 ms.topic: "article"
-author: "JimDaly" #TODO: NoOwner
+author: JimDaly #TODO: NoOwner
 ms.subservice: dataverse-developer
 ms.author: "jdaly" # MSFT alias of Microsoft employees only
 manager: "ryjones" # MSFT alias of manager or PM counterpart

powerapps-docs/developer/data-platform/best-practices/business-logic/do-not-use-parallel-execution-in-plug-ins.md

@@ -1,31 +1,24 @@
 ---
 title: "Do not use parallel execution within plug-ins and workflow activities | MicrosoftDocs"
 description: "Multi or parallel threading within plug-ins or custom workflow activities is not supported."
-services: ''
-suite: powerapps
-documentationcenter: na
-author: JimDaly
-manager: ryjones
-editor: ''
-tags: ''
-
-ms.devlang: na
+ms.date: 04/03/2022
+author: divka78
+ms.author: dikamath
+manager: sunilg
+ms.reviewer: pehecke
 ms.topic: article
-ms.tgt_pltfrm: na
-ms.workload: na
-ms.date:  08/14/2019
 ms.subservice: dataverse-developer
-ms.author: pehecke
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
+contributors:
+ - JimDaly
+ - phecke
 ---
 # Do not use parallel execution within plug-ins and workflow activities
 
-
-
 **Category**: Design, Performance, Security, Supportability
 
 **Impact potential**: High

powerapps-docs/developer/data-platform/best-practices/business-logic/implement-all-types-of-queries-when-filtering-preoperation-retrievemultiple.md

@@ -1,26 +1,22 @@
 ---
 title: "Implement all types of queries when filtering results using PreOperation RetrieveMultiple | MicrosoftDocs"
 description: "For best performance and consistent results for all applications you must implement filtering for all types of queries that can be used with plug-ins that are registered for the PreOperation stage of RetrieveMultiple"
-services: ''
 suite: powerapps
-documentationcenter: na
-author: JimDaly
-manager: ryjones
-editor: ''
-tags: ''
-
-ms.devlang: na
+ms.date: 04/03/2022
+author: divka78
+ms.author: dikamath
+manager: sunilg
+ms.reviewer: pehecke
 ms.topic: article
-ms.tgt_pltfrm: na
-ms.workload: na
-ms.date: 09/23/2019
 ms.subservice: dataverse-developer
-ms.author: jdaly
 search.audienceType: 
   - developer
 search.app: 
   - PowerApps
   - D365CE
+contributors:
+ - JimDaly
+ - phecke
 ---
 # Implement all types of queries when filtering results using PreOperation RetrieveMultiple
 
@@ -77,7 +73,7 @@ If a plug-in is written to change the records returned in a specific application
 
 When using the Web API, GET requests on a collection are converted to <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> unless the query uses FetchXml as described in [Retrieve and execute predefined queries](../../webapi/retrieve-and-execute-predefined-queries.md). In that case the queries use <xref:Microsoft.Xrm.Sdk.Query.FetchExpression>.
 
-The legacy web client for model-driven apps is being replaced by Unified Interface. Unified Interface uses the FetchXml defined in the [SavedQuery.FetchXml](../../reference/entities/savedquery.md#BKMK_FetchXml) or [UserQuery.FetchXml](../../reference/entities/userquery.md#BKMK_FetchXml) properties. For better performance, Unified Interface does not convert the FetchXml data to a <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> before executing these queries as the legacy web client did. Therefore, queries that were modified in plug-in code for the legacy web client which used  <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> will not apply the same changes now that the query to support views is being passed using <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> unless the plug-in code is written to apply same logic to <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> queries. 
+The legacy web client for model-driven apps was replaced by Unified Interface. Unified Interface uses the FetchXml defined in the [SavedQuery.FetchXml](../../reference/entities/savedquery.md#BKMK_FetchXml) or [UserQuery.FetchXml](../../reference/entities/userquery.md#BKMK_FetchXml) properties. For better performance, Unified Interface does not convert the FetchXml data to a <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> before executing these queries as the legacy web client did. Therefore, queries that were modified in plug-in code for the legacy web client which used  <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> will not apply the same changes now that the query to support views is being passed using <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> unless the plug-in code is written to apply same logic to <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> queries. 
 
 <a name='seealso'></a>