Merge remote-tracking branch 'origin/main' into matp-2863997

Author: Mattp123

README.md

@@ -1,10 +1,10 @@
 # Microsoft Power Apps Documentation
 
-This is the GitHub repository for the technical product documentation for **Power Apps**. This documentation is published to  [https://docs.microsoft.com/powerapps](https://docs.microsoft.com/powerapps).
+This is the GitHub repository for the technical product documentation for **Power Apps**. This documentation is published at [Microsoft Power Apps documentation](https://docs.microsoft.com/powerapps).
 
 ## How to contribute
 
-Thanks for your interest in contributing to [docs.microsoft.com](https://docs.microsoft.com/), home of technical content for Microsoft products and services.
+Thanks for your interest in [contributing](https://docs.microsoft.com/), home of technical content for Microsoft products and services.
 
 To learn how to make contributions to the content in this repository, start with our [Docs contributor guide](https://docs.microsoft.com/contribute). If you are a Microsoft employee, please visit the [internal version](https://aka.ms/contributors-guide) of this guide (only accessible to Microsoft employees).
 

powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md

@@ -46,13 +46,13 @@ To add code components to an app, you need to enable the Power Apps component fr
 
 3. On the left pane, select **Environments**, select the environment where you want to enable this feature, and then select **Settings**.
 
-4. On the **Products** tab, select **Features**.
+4. Expand **Product**, and select **Features**.   
+
+5. From the list of available features, turn on **Power Apps component framework for canvas apps**, and then select **Save**.
 
    > [!div class="mx-imgBorder"]
    > ![Enable Power Apps component framework.](media/enable-pcf-feature.png "Enable Power Apps component framework")
 
-5. From the list of available features, turn on **Power Apps component framework for canvas apps**, and then select **Save**.
-
 ## Implementing code components
 
 After you enable the Power Apps component framework feature in your environment, you can start implementing the logic for code components. For a step-by-step tutorial, go to [Create your first code component](implementing-controls-using-typescript.md).

powerapps-docs/developer/component-framework/customize-editable-grid-control.md

@@ -89,6 +89,16 @@ The template control is included in the [PowerApps-Samples](https://github.com/m
 1. Test your customizer by opening the main grid for the customized entity.
 1. Repeat steps 6-11 for any other entities whose grid needs a grid customizer control.
 
+## Best practices
+
+- Cell renderers and editors are user interface components. Do not use them to mutate data or metadata of the grid.
+- The customizer controls should be lightweight and fast so as to not affect overall grid performance.
+- To maintain the design consistency, follow [Fluent design principals](https://www.microsoft.com/design/fluent/#/) and use [Fluent controls](https://developer.microsoft.com/en-us/fluentui#/controls/web) in your customizers.
+- Make sure your custom renderer or editor is accessible.
+- The customizer function should be pure since the grid will call it multiple times to get customized elements and will expect the return value to be consistent.
+- The grid may dispose a customizer element at any time and call to get a new one at any time. Make sure to dispose of any internal state on unmount to prevent memory leaks.
+- Do not use renderers to override the values in the grid since the new values will not be used by the server to do filtering or sorting.
+
 ## Example
 
 You can find an example of a customized editable grid control here: [Customized editable grid](sample-controls/customized-editable-grid-control.md).
@@ -100,4 +110,4 @@ You can find an example of a customized editable grid control here: [Customized
 [Learn Power Apps component framework](/learn/paths/use-power-apps-component-framework)
 
 
-[!INCLUDE [footer-banner](../../includes/footer-banner.md)]
+[!INCLUDE [footer-banner](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/best-practices/business-logic/use-invalidpluginexecutionexception-plugin-workflow-activities.md

@@ -29,11 +29,11 @@ contributors:
 
 ## Symptoms
 
-If a synchronous plug-in returns an exception other than <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> back to the platform, in a Power Apps client an error  is displayed to the user with the message of the exception <xref:System.Exception.Message> and the stack trace. This provides an unfriendly user experience in what is likely already a frustrating situation.
+If a synchronous plug-in returns an exception other than <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> back to the platform, in a Power Apps client an error is displayed to the user with the message of the exception <xref:System.Exception.Message> and the stack trace. This provides an unfriendly user experience in what is likely already a frustrating situation.
 
 If you are using <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> to intentionally cancel the operation because of data validation logic issue, you should provide guidance applicable to the application user so that they can correct the issue and continue.
 
-If the error is unexpected, it is still recommended to catch the error and convert it into a <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> so that applications can show a friendly error message with guidance to help a user or technical staff quickly identify the issue.
+If the error is unexpected, it is still recommended to catch the exception, convert it into a <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException>, and then throw the new exception so that applications can show a friendly error message with guidance to help a user or technical staff quickly identify the issue.
 
 <a name='guidance'></a>
 
@@ -44,7 +44,7 @@ Plug-ins should only return an <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionExc
 - Show a useful message to the user
 - Avoiding event log/trace file bloat
 
-Failure to convert the message into a <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> will result in an `IsvUnExpected` error with no message displayed to the user from a Power Apps client.
+A thrown <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> returns to the caller with a friendly message and an `IsvAborted` error code. Failure to catch and convert an exception into a <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> will result in an `IsvUnExpected` error code with no friendly message displayed to the user from a Power Apps client. 
 
 ### Handle errors from functions called in plug-ins
 

powerapps-docs/developer/data-platform/supported-customizations.md

@@ -24,7 +24,7 @@ You can customize Microsoft Dataverse by using tools that are available in Power
 
 Customizations made using methods other than those described here are unsupported and could cause problems during updates and upgrades to Dataverse. For more information, see [Unsupported Customizations](#unsupported-customizations).
 
-Topics covered in technical articles published on Microsoft sites such as docs.microsoft.com are supported, but might not be upgradable.
+Topics covered in technical articles published on Microsoft sites such as Microsoft Docs are supported, but might not be upgradable.
 
 ## Customizations using Power Apps
 
@@ -127,4 +127,4 @@ The following is a list of unsupported action types that are frequently asked ab
 
 [Supported customizations for model-driven apps](../model-driven-apps/supported-customizations.md)
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/work-event-data-azure-event-hub-solution.md

@@ -30,7 +30,7 @@ Azure Event Hubs is a highly scalable publish-subscribe service that can ingest
 
 You can create an event hub in Azure either through API programming  or interactively by using the [Azure portal](https://portal.azure.com/). Either way, after creating your event hub you must obtain a copy of the event hub connection string and provide that string when registering the Azure service endpoint detailed in the next section.  
 
-For more information about creating event hubs see the [Event Hubs documentation](https://azure.microsoft.com/documentation/services/event-hubs/).  
+For more information about creating event hubs see the [Event Hubs documentation](/azure/event-hubs/).
 
 ## 2. Register an endpoint
 
@@ -58,5 +58,4 @@ You can check the related system job in the Dataverse web application and look f
 
 [Azure integration with Dataverse](azure-integration.md)
 
-
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/retrieveMultipleRecords.md

@@ -105,6 +105,10 @@ The following [Column types](../../../../data-platform/entity-attribute-metadata
 - PartyList
 - Virtual
 
+## Unsupported features in Mobile Offline
+The following features are not supported in Mobile Offline:
+- Grouping and Aggregation features
+
 ## Supported Filter Operations Per Attribute Type in Mobile Offline using FetchXML
 The following operations are supported for all attribute types when working with FetchXML:
 - Equals (`eq`)

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-data/includes/isValid-description.md

@@ -1 +1 @@
-Gets a boolean value indicating whether all of the form data is valid. This includes the main table and any unbound columns. If the form has empty, required columns on it, control-level error notifications is shown.
+Gets a boolean value indicating whether all of the form data is valid. This includes the main table and any unbound columns. If the form has empty required columns on it, control-level error notifications is shown.

powerapps-docs/developer/model-driven-apps/clientapi/reference/save-event-arguments/includes/isDefaultPrevented-description.md

@@ -1 +1 @@
-Returns a value indicating whether the save event has been canceled because the [preventDefault](../preventDefault.md) method was used in this event hander or a previous event handler.
+Returns a value indicating whether the save event has been canceled because the [preventDefault](../preventDefault.md) method was used in this event handler or a previous event handler.

powerapps-docs/learning-catalog/solution-architect.md

@@ -19,7 +19,7 @@ The following catalog is organized from core knowledge to specific domains, and
 | Content | Description | Format | Length |
 |---------|-------------|--------|--------|
 | [Becoming a solution architect for Dynamics 365 and Power Platform](/learn/modules/becoming-solution-architect/) |The Solution Architect leads successful implementations and focuses on how solutions address the broader business and technical needs of organizations.  This module covers what it takes to get started as a Solution Architect and as key member of the overall project team. | Free, self-paced online learning path| 1 hr 43 min |
-| [Solution Architect: Design Microsoft Power Platform solutions](/learn/paths/solution-architect-data/) |A Solution Architect should have functional and technical knowledge of Microsoft Power Platform, Dynamics 365 apps, related Microsoft cloud solutions, and other third-party technologies. This Learning Path looks at architecture, data modeling, security, and related tasks for a solution architect. |Free, self-paced online learning path| 7 hr 6 min |
+| [Solution Architect: Design Microsoft Power Platform solutions](/learn/paths/solution-architect-data/) |A Solution Architect should have functional and technical knowledge of Microsoft Power Platform, Dynamics 365 apps, related Microsoft cloud solutions, and other third-party technologies. This learning path looks at architecture, data modeling, security, and related tasks for a solution architect. |Free, self-paced online learning path| 7 hr 6 min |
 
 ## Exam<a name="exam"></a>