Live publish for 12 July 2024.

Author: bishalgoswami

powerapps-docs/developer/data-platform/fetchxml/reference/attribute.md

@@ -4,7 +4,7 @@ description: Use this element to specify which columns in the containing entity
 author: pnghub
 ms.author: gned
 ms.reviewer: jdaly
-ms.date: 02/29/2024
+ms.date: 07/12/2024
 ms.topic: reference
 ms.subservice: dataverse-developer
 search.audienceType: 
@@ -50,7 +50,7 @@ contributors:
 |`groupby`|No|When you aggregate data, this attribute specifies the column to use to group the data. [Learn more about grouping](../aggregate-data.md#grouping).|
 |`name`|Yes|The logical name of the column.|
 |`rowaggregate`|No|When this value is set to `CountChildren` a value that includes the total number of child records for the record is included in the results. [Learn how to use this attribute](../../query-hierarchical-data.md#retrieve-the-number-of-hierarchically-related-child-records).|
-|`usertimezone`|No|Used by aggregate queries that group by datetime columns. Specifies that the grouping use the user's time zone, otherwise UTC is used. Depending on the time zone, the same datetime value can fall in different days. [Learn about grouping by parts of a date](../aggregate-data.md#grouping-by-parts-of-a-date)|
+|`usertimezone`|No|Used by aggregate queries that group by datetime columns. Depending on the time zone, the same datetime value can fall in different days. [Learn about grouping by parts of a date](../aggregate-data.md#grouping-by-parts-of-a-date)<br /><br />Use this attribute with a `false` value to force the grouping to use UTC value. When you don't set this attribute, the default value is `true`, and the user's time zone is used.<br /><br />**Note**: With QueryExpression, the grouping always uses UTC. When using the SDK [FetchXmlToQueryExpressionRequest class](/dotnet/api/microsoft.crm.sdk.messages.fetchxmltoqueryexpressionrequest), this setting is lost. There's [no way to set this using QueryExpression](../../org-service/queryexpression/aggregate-data.md#time-zone-when-grouping-by-date).|
 
 ## Parent elements
 

powerapps-docs/guidance/coding-guidelines/code-optimization.md

@@ -1,16 +1,15 @@
 ---
 title: Power Apps code optimization
 description: Learn about how to optimize code in Power Apps.
-ms.date: 06/12/2024
+ms.date: 06/25/2024
 ms.topic: conceptual
 ms.subservice: guidance
 ms.service: powerapps
 author: robstand
 ms.author: rachaudh
- 
 ---
 
-# Code Optimization
+# Code optimization
 
 As canvas apps evolve to meet diverse business requirements, the challenge of maintaining optimal performance becomes a critical consideration. The intricacies of data handling, user interface design, and functionality within canvas apps necessitate a nuanced approach to code optimization.
 
@@ -26,9 +25,16 @@ The `With` function evaluates a formula for a single record. The formula can cal
 
 ### Concurrent function
 
-The `Concurrent` function allows multiple formulas specified within the same property to be evaluated at the same time if they have connector or Dataverse calls. Normally, multiple formulas are evaluated by chaining them together with the `;` (semi-colon) operator, which evaluates each formula sequentially. With the `Concurrent` function, the app will evaluate all formulas within a property concurrently even after using the `;` operator. This concurrency helps users wait less for the same result. When data calls don't start until the previous calls finish, the app must wait for the sum of all request times. If data calls start at the same time, the app needs to wait only for the longest request time. [Learn more](/power-platform/power-fx/reference/function-concurrent) about the `Concurrent` function
+The `Concurrent` function allows multiple formulas specified within the same property to be evaluated at the same time if they have connector or Dataverse calls. Normally, multiple formulas are evaluated by chaining them together with the `;` (semi-colon) operator, which evaluates each formula sequentially. With the `Concurrent` function, the app will evaluate all formulas within a property concurrently even after using the `;` operator. This concurrency helps users wait less for the same result. When data calls don't start until the previous calls finish, the app must wait for the sum of all request times. If data calls start at the same time, the app needs to wait only for the longest request time. [Learn more](/power-platform/power-fx/reference/function-concurrent) about the `Concurrent` function.
 
-![A screenshot of a Power Fx formula that uses the Concurrent function](media/image14.png)
+```powerappsfl
+Concurrent(
+    ClearCollect(colAccounts1, Accounts),
+    ClearCollect(colUsers1, Users),
+    ClearCollect(colEnvDef1, 'Environment Variable Definitions'),
+    ClearCollect(colEnvVal1, 'Environment Variable Values')
+);
+```
 
 ### Coalesce Function
 
@@ -193,7 +199,11 @@ The code works as so:
 
 - `Formula` is the output of the function
 
-![A screenshot of the Power Fx window with a user-defined function in the fx box](media/image17.png)
+```powerappsfl
+// Function to calculate the area of a circle based on the radius
+calcAreaOfCircle(radius: Number): Number = 
+    IfError(Pi() * radius * radius, 0);
+```
 
 Use `IfError` to implement error handling within the defined function.
 

powerapps-docs/maker/canvas-apps/controls/control-gallery.md

@@ -47,6 +47,9 @@ The gallery control has these limitations:
 1. You can only add one gallery inside another gallery.
 1. The minimum **TemplateSize** is one. This can cause controls in the **Gallery** to drift from their expected **X** or **Y** values, when you don't account for the template size.
 1. If you generate an app automatically from data, save the app, and then reopen it, the browse gallery might not immediately show any data. To resolve this issue, type at least one character in the search box, and then delete the text that you typed. The gallery will then show the data as expected.
+1. If a gallery includes a ComboBox, DatePicker, Slider, or Toggle control with an `OnChange` rule that patches the same data source or collection as the gallery, it may lead to unexpected or reduced performance. This is because an `OnChange` rule that patches the data source of the gallery can create a never-ending cycle of patching and reloading. To avoid this issue, it is advisable not to use `OnChange` rules when these controls are placed within a gallery.
+
+
 
 
 ## Key properties