Merge branch 'main' into patch-11

Author: mduelae

.openpublishing.redirection.json

@@ -392,7 +392,7 @@
     },
     {
       "source_path": "powerapps-docs/maker/canvas-apps/working-with-environments.md",
-      "redirect_url": "/power-platform/admin/working-with-environments",
+      "redirect_url": "/powerapps/maker/canvas-apps/intro-maker-portal",
       "redirect_document_id": "false"
     },
     {
@@ -512,7 +512,7 @@
     },
     {
       "source_path": "powerapps-docs/administrator/environments-administration.md",
-      "redirect_url": "/power-platform/admin/environments-administration",
+      "redirect_url": "/power-platform/admin/create-environment",
       "redirect_document_id": "false"
     },
     {
@@ -712,7 +712,7 @@
     },
     {
       "source_path": "powerapps-docs/environments-administration.md",
-      "redirect_url": "/powerapps/administrator/environments-administration",
+      "redirect_url": "/power-platform/admin/create-environment",
       "redirect_document_id": "false"
     },
     {
@@ -1812,7 +1812,7 @@
     },
     {
       "source_path": "powerapps-docs/working-with-environments.md",
-      "redirect_url": "/powerapps/maker/canvas-apps/working-with-environments",
+      "redirect_url": "/powerapps/maker/canvas-apps/intro-maker-portal",
       "redirect_document_id": "false"
     },
     {

CODEOWNERS

@@ -3,6 +3,11 @@
 
 /powerapps-docs/                                    @KumarVivek
 /powerapps-docs/administrator/                      @jimholtz @KumarVivek
-/powerapps-docs/developer/                          @PHecke @Nkrb @KumarVivek
-/powerapps-docs/maker/                              @Mattp123 @tapanm-msft @KumarVivek
+/powerapps-docs/developer/                          @PHecke @KumarVivek
+/powerapps-docs/maker/canvas-apps                   @tapanm-msft @KumarVivek
+/powerapps-docs/maker/data-platform                 @Mattp123 @KumarVivek
+/powerapps-docs/maker/model-driven-apps             @Mattp123 @KumarVivek
+/powerapps-docs/maker/common                        @Mattp123 @tapanm-msft @KumarVivek
+/powerapps-docs/maker/portals                       @nickdoelman @KumarVivek
 /powerapps-docs/user/                               @mduelae @KumarVivek
+/powerapps-docs/teams/                              @tapanm-msft @KumarVivek

powerapps-docs/developer/component-framework/media/device-api-control.png

@@ -5,12 +5,10 @@ keywords:
 ms.author: nabuthuk
 author: Nkrb
 manager: kvivek
-ms.date: 12/13/2021
+ms.date: 02/11/2022
 ms.service: "powerapps"
-ms.suite: ""
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 8907f07a-ad45-47e4-a503-8eaae9bba5f7
+ms.subservice: "pcf"
+ms.topic: "reference"
 ---
 
 # DataProviderCapabilities
@@ -51,6 +49,18 @@ If the dataset records can be paged.
 
 Whether adding new records is supported or not.
 
+**Type**: `boolean`
+
+### hasRecordNavigation
+
+Whether the dataset supports record navigation for lookup and primary fields.
+
+**Type**: `boolean`
+
+### hasCellImageInfo
+
+Whether image info for record columns can be retrieved.
+
 **Type** `boolean`
 
 ## Related topics

powerapps-docs/developer/component-framework/reference/DataProviderCapabilities.md

@@ -23,11 +23,13 @@ Model-driven and canvas apps
 
 ## Syntax
 
-`context.parameters.dataset.openDatasetItem(entityreference)`
+`context.parameters.dataset.openDatasetItem(entityReference)`
 
-## Return Value
+## Parameters
 
-**Type**: [Entityreference](../entityreference.md)
+| Parameter Name  | Type                                       | Required | description                    |
+| --------------- | ------------------------------------------ | -------- | ------------------------------ |
+| entityReference | `[Entityreference](../entityreference.md)` | Yes      | Reference that will be opened. |
 
 ### Related topics
 

powerapps-docs/developer/component-framework/reference/dataset/opendatasetitem.md

@@ -5,7 +5,7 @@ keywords:
 ms.author: nabuthuk
 author: Nkrb
 manager: kvivek
-ms.date: 08/09/2021
+ms.date: 02/04/2022
 ms.service: "powerapps"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -47,8 +47,12 @@ Model-driven and canvas apps
   }
 ```
 
-### Related topics
+## Sample controls
+
+[Device API component](../sample-controls/device-api-control.md)  
+[Image upload component](../sample-controls/image-upload-control.md)
 
+### Related topics
 [Power Apps component framework API reference](../reference/index.md)<br/>
 [Power Apps component framework overview](../overview.md)
 

powerapps-docs/developer/component-framework/reference/device.md

@@ -0,0 +1,39 @@
+---
+title: "Device API component | Microsoft Docs"
+description: "This sample component showcases Device API capabilities of the Power Apps control framework."
+ms.custom: ""
+manager: kkaul
+ms.date: 02/02/2022
+ms.service: "powerapps"
+ms.topic: "article"
+ms.author: "vilesyk"
+author: lesyk
+---
+
+# Implementing a Device API component
+
+This sample component showcases Device API capabilities of the Power Apps control framework.
+
+> [!div class="mx-imgBorder"]
+> ![Device API component](../media/device-api-control.png "Device API component")
+
+> [!IMPORTANT]
+> If you want to use the device API methods, you need to declare the usage of these method in the [feature-usage](../manifest-schema-reference/feature-usage.md) node in the manifest file.
+
+## Available for
+
+Model-driven and canvas apps
+
+## Code
+
+You can download the complete sample component from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/DeviceApiControl).
+
+### Related topics
+[Download sample components](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework)<br/>
+[How to use the sample components](../use-sample-components.md)<br/>
+[Image upload component](./image-upload-control.md)<br/>
+[Device API](../reference/device.md)<br/>
+[Power Apps component framework API reference](../reference/index.md)<br/>
+[Power Apps component framework manifest schema reference](../manifest-schema-reference/index.md)
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/component-framework/sample-controls/device-api-control.md

@@ -1,5 +1,5 @@
 ---
-title: " Image Upload component| Microsoft Docs"
+title: "Image Upload component | Microsoft Docs"
 description: "This sample component renders as an `Upload` button to upload the image and a default image when the component loads for the first time."
 ms.custom: ""
 manager: kvivek
@@ -18,7 +18,7 @@ This sample component renders as an `Upload` button to upload the image and a de
 
 The selected image renders within the component. Meanwhile, the `Remove` button is shown if we need to reset. When you click on the `Remove` button, the default image is displayed.
 
-> [!div class="mx-imgBorder"] 
+> [!div class="mx-imgBorder"]
 > ![Image Upload component](../media/image-upload-control.png "Image Upload component")
 
 ## Available for
@@ -50,9 +50,10 @@ The `device.pickFile` method opens a dialog box to select files for the upload.
 > If the same form or table is used on the legacy web client, then the field will show out-of-box text component on legacy web client, where there might have UX issues.  To make it hidden on the legacy web client, we could uncheck the **Visibility** checkbox and check **Hide Default Control** checkbox together.
 
 ### Related topics
-
 [Download sample components](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework)<br/>
 [How to use the sample components](../use-sample-components.md)<br/>
+[Device API component](./device-api-control.md)<br/>
+[Device API](../reference/device.md)<br/>
 [Power Apps component framework API reference](../reference/index.md)<br/>
 [Power Apps component framework manifest schema reference](../manifest-schema-reference/index.md)
 

powerapps-docs/developer/component-framework/sample-controls/image-upload-control.md

@@ -10,7 +10,7 @@
       href: code-components-model-driven-apps.md
     - name: Code components for canvas apps
       href: component-framework-for-canvas-apps.md
-    - name: Code components for portals (Preview)
+    - name: Code components for portals
       href: ../../maker/portals/component-framework.md
   - name: Get Microsoft Power Platform CLI
     href: get-powerapps-cli.md
@@ -68,6 +68,8 @@
       href: sample-controls/control-state-api.md
     - name: Data Set Grid component
       href: sample-controls/data-set-grid-control.md
+    - name: Device API component
+      href: sample-controls/device-api-control.md
     - name: Formatting API component
       href: sample-controls/formatting-api-control.md
     - name: IFRAME component

powerapps-docs/developer/component-framework/toc.yml

@@ -22,7 +22,8 @@ search.app:
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
 > [!IMPORTANT]
-> To use this capability you must first enable the Application Insights integration preview feature. More information: [Preview: Analyze model-driven apps and Microsoft Dataverse telemetry with Application Insights](/power-platform/admin/analyze-telemetry)
+> To use this capability you must first enable the Application Insights integration preview feature. More information: [Preview: Analyze model-driven apps and Microsoft Dataverse telemetry with Application Insights](/power-platform/admin/analyze-telemetry)<p/>
+> There is presently no support of `ILogger` within a plug-in profiling/debug session of the Plug-in Registration tool or the Power Platform Tools extension for Visual Studio.
 
 When you enable Application Insights for your organization, any plug-ins written using the [ILogger Interface](/dotnet/api/microsoft.xrm.sdk.plugintelemetry.ilogger) provided in the Organization Service SDK assemblies will write telemetry to your Application Insights resource.