Merge branch 'main' into 2612854-2

Author: tapanm-MSFT

.openpublishing.redirection.json

@@ -1,5 +1,45 @@
 {
   "redirections": [
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection.md",
+      "redirect_url": "formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/getVisible.md",
+      "redirect_url": "../formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-footerSection/setVisible.md",
+      "redirect_url": "../formcontext-ui#formcontextuifootersection-removed",
+      "redirect_document_id": "false"
+    },
+    {
+      "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",
@@ -1172,7 +1212,7 @@
     },
     {
       "source_path": "powerapps-docs/controls/control-text-input.md",
-      "redirect_url": "/powerapps/maker/canvas-apps/controls/control-text-input",
+      "redirect_url": "/power-apps/maker/canvas-apps/controls/control-text-input",
       "redirect_document_id": "false"
     },
     {

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/implementing-controls-using-typescript.md

@@ -73,6 +73,12 @@ To create a new project:
    > [!NOTE]
    > If you receive the error `The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program.`, make sure you have installed [node.js](https://nodejs.org/en/download/) (LTS version is recommended) and all other prerequisites.
 
+1. After npm install, you will need to generate ManifestDesignTypes.d.ts file in this directory using the below command."
+   ```
+   npm run refreshTypes
+   ```
+ 
+   
 ## Implementing manifest
 
 The control manifest is an XML file that contains the metadata of the code component. It also defines the behavior of the code component. In this tutorial, this manifest file is created under the `LinearInputControl` subfolder. When you open the `ControlManifest.Input.xml` file in Visual Studio Code, you'll notice that the manifest file is predefined with some properties. More information: [Manifest](manifest-schema-reference/manifest.md).

powerapps-docs/developer/component-framework/manifest-schema-reference/code.md

@@ -6,12 +6,12 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
 
 ms.suite: ""
 ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"

powerapps-docs/developer/component-framework/manifest-schema-reference/control.md

@@ -6,12 +6,9 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"
@@ -31,7 +28,7 @@ Model-driven and canvas apps
 |--|--|--|--|--------|
 |`namespace`|Defines the object prototype of the component|[!INCLUDE [alphanumerictype-description](includes/alphanumerictype-description.md)]|Yes|Model-driven and canvas apps |
 |`constructor`|A method for initializing the object|[!INCLUDE [alphanumerictype-description](includes/alphanumerictype-description.md)]|Yes|Model-driven and canvas apps |
-|`control-type`|Standard|[!INCLUDE [controltype-description](includes/controltype-description.md)]|No|Model-driven and canvas apps |
+|`control-type`|Whether the control is a standard control or a React control. The value of `virtual` indicates a React control using platform React library. Virtual controls are a feature in public preview. More information: [React controls & platform libraries (Preview) ](../react-controls-platform-libraries.md)|[!INCLUDE [controltype-description](includes/controltype-description.md)]|No|Model-driven and canvas apps |
 |`description-key`|Defines the description of the component that will be seen on the UI.|`string`|No|Model-driven and canvas apps |
 |`display-name-key`|Defines the name of the control that is displayed on the UI.|`string`|Yes|Model-driven and canvas apps  |  
 |`preview-image`|Image that will be used on the customization screens to show a preview of the component.|`string`|No|Model-driven apps|
@@ -69,4 +66,4 @@ Model-driven and canvas apps
 [Power Apps component framework overview](../overview.md)
 
 
-[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/component-framework/manifest-schema-reference/css.md

@@ -6,12 +6,9 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"

powerapps-docs/developer/component-framework/manifest-schema-reference/data-set.md

@@ -6,12 +6,9 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"

powerapps-docs/developer/component-framework/manifest-schema-reference/feature-usage.md

@@ -6,12 +6,9 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 ---
 
 # feature-usage element
@@ -32,7 +29,7 @@ Model-driven apps
 
 |Element|Description|Available for|
 |--|--|-----|
-|[uses-feature](uses-feature.md)|Indicates which feature their components want to use.|Model-driven apps|
+|[uses-feature](uses-feature.md)|[!INCLUDE [uses-feature-description](includes/uses-feature-description.md)]|Model-driven apps|
 
 
 ## Example

powerapps-docs/developer/component-framework/manifest-schema-reference/html.md

@@ -1,17 +1,14 @@
 ---
 title: HTML Element | Microsoft Docs
-description: 
+description: Use HTML web resources to create user interface elements for client extensions. 
 keywords:
 ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"

powerapps-docs/developer/component-framework/manifest-schema-reference/img.md

@@ -6,12 +6,9 @@ ms.subservice: pcf
 ms.author: jdaly
 author: noazarur-microsoft
 manager: kvivek
-ms.date: 03/12/2022
+ms.date: 03/26/2022
 ms.reviewer: jdaly
-
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
+ms.topic: "reference"
 applies_to: 
   - "Dynamics 365 (online)"
   - "Dynamics 365 Version 9.x"