Live publish for 12 July 2024.

bishalgoswami · web-flow · commit b156c273b39b · 2024-07-13T00:30:23.000+05:30
diff --git a/powerapps-docs/developer/data-platform/webapi/compose-http-requests-handle-errors.md b/powerapps-docs/developer/data-platform/webapi/compose-http-requests-handle-errors.md
@@ -172,7 +172,7 @@ When you execute batch operations, you must apply many different headers in the
 |`304 Not Modified`|Expect this status code when testing whether an entity has been modified since it was last retrieved. More information: [Conditional retrievals](perform-conditional-operations-using-web-api.md#bkmk_DetectIfChanged)|Redirection|  
 |`403 Forbidden`|Expect this  status code for the following types of errors:<br /><br />- `AccessDenied`<br />- `AttributePermissionReadIsMissing`<br />- `AttributePermissionUpdateIsMissingDuringUpdate`<br />- `AttributePrivilegeCreateIsMissing`<br />-   `CannotActOnBehalfOfAnotherUser`<br />- `CannotAddOrActonBehalfAnotherUserPrivilege`<br />- `CrmSecurityError`<br />- `InvalidAccessRights`<br />- `PrincipalPrivilegeDenied`<br />- `PrivilegeCreateIsDisabledForOrganization`<br />- `PrivilegeDenied`<br />- `unManagedinvalidprincipal`<br />- `unManagedinvalidprivilegeedepth`|Client Error|  
 |`401 Unauthorized`|Expect this status code for the following types of errors:<br /><br />- `BadAuthTicket`<br />- `ExpiredAuthTicket`<br />-   `InsufficientAuthTicket`<br />- `InvalidAuthTicket`<br />- `InvalidUserAuth`<br />- `MissingCrmAuthenticationToken`<br />- `MissingCrmAuthenticationTokenOrganizationName`<br />- `RequestIsNotAuthenticated`<br />- `TamperedAuthTicket`<br />- `UnauthorizedAccess`<br />-   `UnManagedInvalidSecurityPrincipal`|Client Error|  
-|`413 Payload Too Large`|Expect this  status code when the request length is too large.|Client Error|  
+|`413 Payload Too Large`|Expect this  status code when the request length is too large. [Learn about request and response payload size limitations](../work-with-data.md#request-and-response-payload-size-limitations)|Client Error|  
 |`400 BadRequest`|Expect this  status code when an argument is invalid.|Client Error|  
 |`404 Not Found`|Expect this  status code when the resource doesn't exist.|Client Error|  
 |`405 Method Not Allowed`|This error occurs for incorrect method and resource combinations. For example, you can't use DELETE or PATCH on a collection of entities.<br /><br /> Expect this for the following types of errors:<br /><br />- `CannotDeleteDueToAssociation`<br />-   `InvalidOperation`<br />- `NotSupported`|Client Error|  
diff --git a/powerapps-docs/developer/data-platform/work-with-data.md b/powerapps-docs/developer/data-platform/work-with-data.md
@@ -40,11 +40,11 @@ Dataverse provides two ways to retrieve, add, and modify data: SDK for .NET & We
 If you are working with .NET, we recommend using our [SDK for .NET](org-service/overview.md).
 
 - Use the [ServiceClient class](/dotnet/api/microsoft.powerplatform.dataverse.client.serviceclient) in the [DataverseServiceClient NuGet package](https://www.nuget.org/packages/Microsoft.PowerPlatform.Dataverse.Client/) if you have a client application.
-- Use the [Microsoft.CrmSdk.CoreAssemblies NuGet package](https://www.nuget.org/packages/Microsoft.CrmSdk.CoreAssemblies/) when you are writing a plug-in or custom workflow activity.
+- Use the [Microsoft.CrmSdk.CoreAssemblies NuGet package](https://www.nuget.org/packages/Microsoft.CrmSdk.CoreAssemblies/) when you're writing a plug-in or custom workflow activity.
 
 The Dataverse SDK for .NET supports build targets for both .NET Framework and .NET 6+. However, plug-in and custom workflow activities must use .NET Framework.
 
-If you are using our [PowerShell module](https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/) or using our [custom log-in control](xrm-tooling/use-xrm-tooling-common-login-control-client-applications.md) with a Windows client application, use the [the Xrm.Tooling](xrm-tooling/build-windows-client-applications-xrm-tools.md)
+If you're using our [PowerShell module](https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/) or using our [custom log-in control](xrm-tooling/use-xrm-tooling-common-login-control-client-applications.md) with a Windows client application, use the [the Xrm.Tooling](xrm-tooling/build-windows-client-applications-xrm-tools.md)
 
 - [Use the SDK for .NET](org-service/overview.md)
 - [Quickstart: Execute an SDK for .NET request (C#)](org-service/quick-start-org-service-console-app.md)
@@ -75,10 +75,12 @@ The [Power Query Dataverse connector](/power-query/connectors/dataverse) uses th
 [Learn to use SQL to query data](dataverse-sql-query.md)
 
 
-## Limitations
+## Request and Response payload size limitations
 
-There's a 1-GB size limitation on the size of a response that Dataverse returns.  Few APIs or queries are capable of returning this much data.  If you encounter this limit, you should consider what other options are available to get the data in multiple, smaller requests.
+The maximum payload size for any request sent to Dataverse is 128 MB. Requests with payloads over this limit receive a [413 Payload Too Large](https://devdoc.net/web/developer.mozilla.org/docs/Web/HTTP/Status/413.html) HTTP status code in the response.
 
-The deprecated SOAP endpoint returns serialized XML data that is much more verbose than the serialized JSON data returned by the Web API. If you're using the deprecated SOAP endpoint, you should use the Web API equivalent operation. More information: [About the legacy SOAP endpoint](org-service/overview.md#about-the-legacy-soap-endpoint)
+There's a 1-GB size limitation on the size of a response that Dataverse returns. Few APIs or queries are capable of returning this much data.  If you encounter this limit, you should consider what other options are available to get the data in multiple, smaller requests.
+
+The deprecated SOAP endpoint payloads use serialized XML data that is much more verbose than the serialized JSON data payloads the Web API uses. You're less likely to encounter errors where the request or response payload is too large when you use the Web API. [Learn about the legacy SOAP endpoint](org-service/overview.md#about-the-legacy-soap-endpoint)
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/maker/common/performance-insights-overview.md b/powerapps-docs/maker/common/performance-insights-overview.md
@@ -2,9 +2,8 @@
 title: "Overview of performance insights in Power Apps | MicrosoftDocs"
 description: Understand performance insights. 
 ms.custom: ""
-ms.date: 06/15/2021
+ms.date: 07/10/2024
 ms.reviewer: ""
-
 ms.topic: overview
 author: "Mattp123"
 ms.subservice: common
@@ -14,6 +13,9 @@ search.audienceType:
 ---
 # What are performance insights? (preview)
 
+> [!IMPORTANT]
+> This feature is undergoing significant improvements and until the new version becomes available the current feature is disabled.
+
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
 Performance insights are a self-service tool for enterprise app makers that analyzes runtime user data and provides a prioritized list of recommendations to help improve the performance of model-driven apps. This feature provides a daily set of analytic insights related to the performance of a Power Apps model-driven or customer engagement app, such as Dynamics 365 Sales or Dynamics 365 Service, with recommendations and actionable items. Enterprise app makers can view detailed performance insights at an app-level in the [Power Apps portal](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
