Merge remote-tracking branch 'origin/main' into fafuxa-ms-patch-6

Author: Mattp123

.openpublishing.redirection.json

@@ -1,17 +1,42 @@
 {
   "redirections": [
     {
-      "source_path": "powerapps-docs/maker/data-platform/data-platform-cr.md",
-      "redirect_url": "create-edit-entities-portal",
+      "source_path": "powerapps-docs/maker/portals/known-issues.md",
+      "redirect_url": "/power-pages/known-issues",
       "redirect_document_id": false
     },
     {
-      "source_path": "powerapps-docs/cards/controls/repeat-for-every.md",
-      "redirect_url": "/power-apps/cards/controls/control-reference#r",
+      "source_path": "powerapps-docs/maker/portals/configure/search.md",
+      "redirect_url": "/power-pages/configure/search/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/search-additional-entities.md",
+      "redirect_url": "/power-pages/configure/search/additional-tables",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/improve-portal-search-faceted-search.md",
+      "redirect_url": "/power-pages/configure/search/faceted",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/search-file-attachment.md",
+      "redirect_url": "/power-pages/configure/search/file-attachment",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/portals/configure/progressive-search.md",
+      "redirect_url": "/power-pages/configure/search/progressive",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/maker/data-platform/data-platform-cr.md",
+      "redirect_url": "create-edit-entities-portal",
       "redirect_document_id": false
     },
     {
-      "source_path": "powerapps-docs/cards/controls/repreat-for-every.md",
+      "source_path": "powerapps-docs/cards/controls/repeat-for-every.md",
       "redirect_url": "/power-apps/cards/controls/control-reference#r",
       "redirect_document_id": false
     },
@@ -25,6 +50,16 @@
       "redirect_url": "overview",
       "redirect_document_id": false
     },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/annotation-note-entity.md",
+      "redirect_url": "attachment-annotation-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "powerapps-docs/developer/data-platform/org-service/samples/upload-retrieve-download-attachment.md",
+      "redirect_url": "attachment-annotation-files",
+      "redirect_document_id": false
+    },
     {
       "source_path": "powerapps-docs/maker/portals/embed-portal-website.md",
       "redirect_url": "/power-pages/configure/embed-website",

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

@@ -3,8 +3,7 @@ title: Control Element | Microsoft Docs
 description: Defines the component's namespace, version and display information.
 ms.author: noazarur
 author: noazarur-microsoft
-manager: lwelicki
-ms.date: 11/21/2022
+ms.date: 02/22/2023
 ms.reviewer: jdaly
 ms.topic: reference
 ms.subservice: pcf
@@ -28,7 +27,7 @@ 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`|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  |  
+|`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|
 |`version`|Defines the version of the component defined in [Semantic Versioning](https://semver.org)|`string`|Yes|Model-driven and canvas apps |
 <!--|`hidden`|Defines whether the component should be hidden or not|[!INCLUDE [booleantype-description](includes/booleantype-description.md)]| No|Model-driven apps|-->
@@ -44,6 +43,7 @@ Model-driven and canvas apps
 |Element|Description|Occurrences|
 |--|--|--|
 |[data-set](data-set.md)|[!INCLUDE [data-set-description](includes/data-set-description.md)]|0 or more|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|0 or 1|
 |[property](property.md)|[!INCLUDE [property-description](includes/property-description.md)]|0 or more|
 |[resources](resources.md)|[!INCLUDE [resources-description](includes/resources-description.md)]|1|
 |[type-group](type-group.md)|[!INCLUDE [type-group-description](includes/type-group-description.md)]|0 or more|
@@ -52,9 +52,13 @@ Model-driven and canvas apps
 ## Example
 
 ```xml
-<control namespace="MyNameSpace" constructor="JSHelloWorldControl" version="1.0.0"
- display-name-key="JS_HelloWorldControl_Display_Key" description-key="JS_HelloWorldControl_Desc_Key"
- control-type="standard" preview-image="img/preview.png">
+<control namespace="MyNameSpace"
+   constructor="JSHelloWorldControl"
+   version="1.0.0"
+   display-name-key="JS_HelloWorldControl_Display_Key"
+   description-key="JS_HelloWorldControl_Desc_Key"
+   control-type="standard"
+   preview-image="img/preview.png">
 </control>
   ```
 

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

@@ -0,0 +1,42 @@
+---
+title: ___domain element | Microsoft Docs
+description: Indicates the ___domain that the external-usage-element applies to.
+ms.author: noazarur
+author: noazarur-microsoft
+ms.date: 02/22/2023
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+# ___domain Element
+
+[!INCLUDE [___domain-description](includes/___domain-description.md)]
+
+## Available for
+
+Canvas apps
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|
+
+## Example
+
+```xml
+<external-service-usage enabled="true">
+   <___domain>www.Microsoft.com</___domain>
+</external-service-usage>
+```
+
+### Related topics
+
+[Power Apps component framework manifest schema reference](index.md)<br/>
+[Power Apps component framework API reference](../reference/index.md)<br/>
+[Power Apps component framework overview](../overview.md)
+
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

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

@@ -0,0 +1,71 @@
+---
+title: external-service-usage element | Microsoft Docs
+description: Indicates whether this control is using external service or not.
+ms.author: noazarur
+author: noazarur-microsoft
+ms.date: 02/22/2023
+ms.reviewer: jdaly
+ms.topic: reference
+ms.subservice: pcf
+contributors:
+ - JimDaly
+---
+# external-service-usage element
+
+[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]
+
+## Available for
+
+Canvas apps
+
+## Parent Elements
+
+|Element|Description|
+|--|--|
+|[control](control.md)|[!INCLUDE [control-description](includes/control-description.md)]|
+
+## Child Elements
+
+
+|Element|Description|Occurrences|Available for|
+|--|--|--|-------|
+|[___domain](___domain.md)|[!INCLUDE [___domain-description](includes/___domain-description.md)]|0 or more|Canvas apps |
+
+
+## Example 1
+
+External usage enabled for www.microsoft.com only.
+
+```xml
+<external-service-usage enabled="true">
+   <___domain>www.Microsoft.com</___domain>
+</external-service-usage>
+```
+
+## Example 2
+
+External usage enabled for multiple domains.
+
+```xml
+<external-service-usage enabled="false">
+  <___domain>www.contoso.com</___domain>
+  <___domain>www.yourcompany.com</___domain>
+</external-service-usage>
+```
+
+## Example 3
+
+External usage is not enabled.
+
+```xml
+<external-service-usage enabled="false" />
+```
+
+### Related topics
+
+[Power Apps component framework manifest schema reference](index.md)<br/>
+[Power Apps component framework API reference](../reference/index.md)<br/>
+[Power Apps component framework overview](../overview.md)
+
+
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/developer/component-framework/manifest-schema-reference/includes/___domain-description.md

@@ -0,0 +1 @@
+Specifies the ___domain within the [external-service-usage element](../external-service-usage.md)

powerapps-docs/developer/component-framework/manifest-schema-reference/includes/external-service-usage-description.md

@@ -0,0 +1 @@
+Indicates whether this control is using external service or not. If it is, set the enabled attribute flag as true and add the external service ___domain to the `<___domain>` property. A control that uses any external service is a premium control and the end user will need a Power Apps license to open an app with a premium control. More information: [Licensing](../../overview.md#licensing)

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

@@ -3,8 +3,7 @@ title: Power Apps component framework manifest schema reference | Microsoft Docs
 description: This section contains reference documentation for manifest schema generated using Microsoft Power Platform CLI.
 ms.author: noazarur
 author: noazarur-microsoft
-manager: lwelicki
-ms.date: 05/27/2022
+ms.date: 02/22/2023
 ms.reviewer: jdaly
 ms.topic: reference
 ms.subservice: pcf
@@ -17,14 +16,16 @@ contributors:
 This section contains reference documentation for manifest schema generated using Microsoft Power Platform CLI.
 
 > [!IMPORTANT]
-> The **Available for** tab shows which elements are supported by model-driven and canvas apps. It is recommended to check the **Available for** section for each individual property whether it is supported or not. For example, the **code** element is supported for both model-driven and canvas apps, but **html** and **img** properties in **code** elements doesn't support canvas apps. 
+> The **Available for** tab shows which elements are supported by model-driven and canvas apps. It is recommended to check the **Available for** section for each individual property whether it is supported or not. For example, the **code** element is supported for both model-driven and canvas apps, but **html** and **img** properties in **code** elements doesn't support canvas apps.
 
 |Element|Description|Available for|
 |----|-----------|-----|
 |[code](code.md)|[!INCLUDE [code-description](includes/code-description.md)]|Model-driven and canvas apps|
 |[control](control.md)|[!INCLUDE [control-description](includes/control-description.md)]|Model-driven and canvas apps|
 |[css](css.md)|[!INCLUDE [css-description](includes/css-description.md)]|Model-driven and canvas apps|
 |[data-set](data-set.md)|[!INCLUDE [data-set-description](includes/data-set-description.md)]|Model-driven apps|
+|[___domain](___domain.md)|[!INCLUDE [___domain-description](includes/___domain-description.md)]|Canvas apps|
+|[external-service-usage](external-service-usage.md)|[!INCLUDE [external-service-usage-description](includes/external-service-usage-description.md)]|Canvas apps|
 |[feature-usage](feature-usage.md)|The feature-usage element acts as a wrapper around the `uses-feature` elements, which themselves allow developers to declare which features their component wants to use. If there are no uses-feature elements defined, the feature-usage element is not required.|Model-driven apps|
 |[img](img.md)|[!INCLUDE [img-description](includes/img-description.md)]|Model-driven apps|
 |[manifest](manifest.md)|Manifest is the metadata file that defines a component. It is an XML document that describes<br/> - The namespace of the component.<br/> - The kind of data it can be configured, either a field or a data-set.<br/> - Any properties that can be configured in the application when the component is added.<br/> - A list of resource files that the component needs.<br/> - One of them must be a JavaScript web resource. This JavaScript must include a function that will instantiate an object. This implements an interface that exposes methods that are required for the component to work. This is called the component implementation library.<br/> - The name of a JavaScript function in the component implementation library that will return an object that applies the required interface.<br/> When someone configures a component in the application, the data in the manifest filters out the available components so that only valid components for the context are available for configuration. The properties defined in the manifest for a component are rendered as configuration fields so that the person configuring the control can specify values. These property values are then available to your component function at run time.|Model-driven and canvas apps|

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

@@ -442,6 +442,10 @@ items:
         href: manifest-schema-reference/css.md
       - name: data-set
         href: manifest-schema-reference/data-set.md
+      - name: ___domain
+        href: manifest-schema-reference/___domain.md
+      - name: external-service-usage
+        href: manifest-schema-reference/external-service-usage.md
       - name: feature-usage
         href: manifest-schema-reference/feature-usage.md
       - name: img

powerapps-docs/developer/data-platform/TOC.yml

@@ -84,10 +84,15 @@
       href: query-throttling.md
     - name: Query Hierarchical data
       href: query-hierarchical-data.md
-    - name: Use image column data
-      href: image-column-data.md
-    - name: Use file column data
-      href: file-column-data.md
+    - name: Files and images overview
+      href: files-images-overview.md
+      items:
+      - name: Use file column data
+        href: file-column-data.md
+      - name: Use image column data
+        href: image-column-data.md
+      - name: Use Attachments and Annotations
+        href: attachment-annotation-files.md
     - name: Audit data changes
       items:
         - name: Overview
@@ -281,8 +286,6 @@
               href: update-recurring-appointment.md
             - name: Link custom columns of the recurring appointment master and appointment tables
               href: link-custom-attributes-recurring-master-appointment-entities.md
-    - name: Annotation (note) table
-      href: annotation-note-entity.md
     - name: Calendar tables
       href: calendar-entities.md
       items:

powerapps-docs/developer/data-platform/analyze-performance.md

@@ -1,7 +1,7 @@
 ---
 title: "Analyze plug-in performance (Microsoft Dataverse) | Microsoft Docs"
 description: "Learn how to find and analyze performance data on plug-ins execution."
-ms.date: 03/22/2022
+ms.date: 02/23/2023
 ms.reviewer: "pehecke"
 ms.topic: "article"
 author: "divkamath"
@@ -18,12 +18,43 @@ contributors:
 ---
 # Analyze plug-in performance
 
-In addition to using a debugger and profiler to learn how your plug-in is performing at the code level, you can obtain metrics as to the overall performance of your registered plug-ins in an organization through [Microsoft Dataverse analytics](/power-platform/admin/analytics-common-data-service).
+When you add business logic to your plug-in you should be aware of the impact your plug-ins will have on overall system performance.
+
+## Time and resource constraints
+
+There is a **2-minute time limit** for a Dataverse message operation to complete. This limit includes executing all registered synchronous plug-ins. There are also limitations on the amount of CPU and memory resources that can be used by extensions. If the limits are exceeded an exception is thrown and the operation will be cancelled.
+
+If the time limit is exceeded, an <xref:System.TimeoutException> will be thrown. If any custom extension exceeds threshold CPU, memory, or handle limits or is otherwise unresponsive, that process will be killed by the platform. At that point any current extension in that process will fail with exceptions. However, the next time that the extension is executed it will run normally.
+
+## Monitor performance
+
+Run-time information about plug-ins and custom workflow extensions is captured and stored in the [PluginTypeStatistic Table](reference/entities/plugintypestatistic.md). These records are populated within 30 minutes to one hour after the custom code executes. This table provides the following data points:
+
+|**Column**|**Description**|
+|--|--|
+|AverageExecuteTimeInMilliseconds|The average execution time (in milliseconds) for the plug-in type. |
+|CrashContributionPercent|The plug-in type percentage contribution to crashes. |
+|CrashCount|Number of times the plug-in type has crashed. |
+|CrashPercent|Percentage of crashes for the plug-in type. |
+|ExecuteCount|Number of times the plug-in type has been executed. |
+|FailureCount |Number of times the plug-in type has failed. |
+|FailurePercent|Percentage of failures for the plug-in type. |
+|PluginTypeIdName|Unique identifier of the user who last modified the plug-in type statistic. |
+|TerminateCpuContributionPercent |The plug-in type percentage contribution to Worker process termination due to excessive CPU usage. |
+|TerminateHandlesContributionPercent |The plug-in type percentage contribution to Worker process termination due to excessive handle usage. |
+|TerminateMemoryContributionPercent|The plug-in type percentage contribution to Worker process termination due to excessive memory usage. |
+|TerminateOtherContributionPercent|The plug-in type percentage contribution to Worker process termination due to unknown reasons. |
+
+## Plug-in performance analytics
+
+In addition to using a debugger and profiler to learn how your plug-in is performing at the code level, you can interactively obtain metrics as to the overall performance of your registered plug-ins in an organization through [Microsoft Dataverse analytics](/power-platform/admin/analytics-common-data-service).
 
 Through the [Plug-in](/power-platform/admin/analytics-common-data-service#plug-ins) dashboard you can view metrics such as average execution time, failures, most active plug-ins, and more.
 
 ![Analytics plug-in dashboard.](media/cds-insights-plugins.png)
 
+To access the dashboard, navigate to [Power Platform Admin Center](https://admin.powerplatform.microsoft.com/). Select **Analytics** > **Dataverse** > **Plug-ins**.
+
 ## See also
 
 [Use plug-ins to extend business processes](plug-ins.md)