Merge branch 'main' into guidance-guidelines-fixes

Author: mduelae

.openpublishing.redirection.json

@@ -1,5 +1,45 @@
 {
   "redirections": [
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md",
+      "redirect_url": "query/overview",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#select-columns",
+      "redirect_url": "query/select-columns",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#join-tables",
+      "redirect_url": "query/join-tables",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#order-rows",
+      "redirect_url": "query/order-rows",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#filter-rows",
+      "redirect_url": "query/filter-rows",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#page-results",
+      "redirect_url": "query/page-results",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#aggregate-data",
+      "redirect_url": "query/aggregate-data",
+      "redirect_document_id": "false"
+   },
+   {
+      "source_path": "powerapps-docs/developer/data-platform/webapi/query-data-web-api.md#count-number-of-rows",
+      "redirect_url": "query/count-rows",
+      "redirect_document_id": "false"
+   },
    {
       "source_path": "powerapps-docs/developer/data-platform/bypass-custom-business-logic.md#bypass-power-automate-flows",
       "redirect_url": "bypass-power-automate-flows",

powerapps-docs/cards/manage-cards/delete-cards.md

@@ -13,7 +13,7 @@ ms.collection:
 
 # Delete a card
 
-To delete a card, you need to be the app owner. An administrator, such as Global admin, Microsoft Entra Global admin, or Dynamics 365 admin can't delete card.
+To delete a card, you need to be the app owner. An admin can't delete a card.
 
 1. Sign in to [Power Apps](https://make.powerapps.com).
 1. From the [left navigation](../../maker/canvas-apps/intro-maker-portal.md#1--left-navigation-pane), select **Cards**.  

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -902,7 +902,7 @@ Follow these steps to create and import a [solution](../../maker/data-platform/s
    >
    > `[Environment URI]/api/data/v9.2/publishers?$select=uniquename,customizationprefix`
    >
-   > More information: [Query data using the Web API](../data-platform/webapi/query-data-web-api.md)
+   > More information: [Query data using the Web API](../data-platform/webapi/query/overview.md)
 
 
 

powerapps-docs/developer/data-platform/asynchronous-service.md

@@ -92,7 +92,7 @@ You can use the following examples to retrieve System Job data.
 
 #### [Web API](#tab/webapi)
 
-Use the following Web API Query to retrieve the columns in the table above. [Learn how to query data using the Web API](webapi/query-data-web-api.md)
+Use the following Web API Query to retrieve the columns in the table above. [Learn how to query data using the Web API](webapi/query/overview.md
 
 ```http
 GET <organization URL>/api/data/v9.2/asyncoperations?$top=1000
@@ -291,7 +291,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn how to query data using the Web API](webapi/query-data-web-api.md)
+[Learn how to query data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -356,7 +356,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn to query data using the Web API](webapi/query-data-web-api.md)
+[Learn to query data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -436,7 +436,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)
+[Learn to query Data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -524,7 +524,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)
+[Learn to query Data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -604,7 +604,7 @@ OData-MaxVersion: 4.0
 OData-Version: 4.0
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)
+[Learn to query Data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -657,7 +657,7 @@ OData-MaxVersion: 4.0
 OData-Version: 4.0
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)
+[Learn to query Data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -713,7 +713,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)
+[Learn to query Data using the Web API](webapi/query/overview.md)
 
 #### [FetchXml](#tab/fetchxml)
 
@@ -779,7 +779,7 @@ OData-Version: 4.0
 Prefer: odata.include-annotations="OData.Community.Display.V1.FormattedValue"
 ```
 
-[Learn to query Data using the Web API](webapi/query-data-web-api.md)   
+[Learn to query Data using the Web API](webapi/query/overview.md)   
 
 
 #### [FetchXml](#tab/fetchxml)

powerapps-docs/developer/data-platform/attachment-annotation-files.md

@@ -1040,7 +1040,7 @@ OData-Version: 4.0
 }
 ```
 
-More information: [Query data using the Web API](webapi/query-data-web-api.md)
+More information: [Query data using the Web API](webapi/query/overview.md)
 
 ---
 

powerapps-docs/developer/data-platform/auditing/retrieve-audit-data.md

@@ -424,7 +424,7 @@ Use this message to retrieve the audit details for a single audit record.
 
 # [Web API](#tab/webapi)
 
-<xref:Microsoft.Dynamics.CRM.RetrieveAuditDetails> is a function bound to the audit table. Include the `Prefer: odata.include-annotations="*"` request header to get [formatted values](../webapi/query-data-web-api.md#formatted-values).
+<xref:Microsoft.Dynamics.CRM.RetrieveAuditDetails> is a function bound to the audit table. Include the `Prefer: odata.include-annotations="*"` request header to get [formatted values](../webapi/query/select-columns.md#formatted-values).
 
 The following example shows the [AttributeAuditDetail ComplexType](xref:Microsoft.Dynamics.CRM.AttributeAuditDetail) returned when the `parentaccountid` is set on an `account` record.
 

powerapps-docs/developer/data-platform/bypass-custom-business-logic.md

@@ -225,7 +225,7 @@ In this case, there's only one: `4ab978b0-1d77-ec11-8d21-000d3a554d57`
 }
 ```
 
-[Learn more about querying data using Web API](webapi/query-data-web-api.md)
+[Learn more about querying data using Web API](webapi/query/overview.md)
 
 
 #### Query your environment with FetchXml

powerapps-docs/developer/data-platform/custom-api-tables.md

@@ -38,7 +38,7 @@ You can use the following queries to retrieve data about custom APIs.
 
 # [Web API](#tab/webapi)
 
- More information: [Query Data using the Web API](webapi/query-data-web-api.md)
+ More information: [Query Data using the Web API](webapi/query/overview.md)
 
 ```http
 GET [Organization URI]/api/data/v9.1/customapis?$select=

powerapps-docs/developer/data-platform/fetchxml/count-rows.md

@@ -38,7 +38,7 @@ When the `returntotalrecordcount` attribute value is `true`, the <xref:Microsoft
 
 ## [Web API](#tab/webapi)
 
-Setting the `returntotalrecordcount` attribute value to `true` has the same result as setting the OData `$count` query option. You can append `&$count=true` to your FetchXml query to get the same results. [Learn more about the OData $count query option](../webapi/query-data-web-api.md#count-number-of-rows).
+Setting the `returntotalrecordcount` attribute value to `true` has the same result as setting the OData `$count` query option. You can append `&$count=true` to your FetchXml query to get the same results. [Learn more about the OData $count query option](../webapi/query/count-rows.md).
 
 When you set the `returntotalrecordcount` attribute (or use the `$count` query option) the data returned includes the `@odata.count` annotation with the total number of records that match the filter criteria, up to 5000.
 

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