Merge pull request #6470 from MicrosoftDocs/jdaly-main-join-limit-raised-to-15

Jdaly main join limit raised to 15

Author: JimDaly

powerapps-docs/developer/data-platform/webapi/retrieve-entity-using-web-api.md

@@ -1,7 +1,7 @@
 ---
 title: "Retrieve a table row using the Web API (Microsoft Dataverse)| Microsoft Docs"
 description: "Read how to form a GET request using the Microsoft Dataverse Web API to retrieve table data specified as the resource with a unique identifier"
-ms.date: 04/19/2022
+ms.date: 06/03/2022
 author: divka78
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -416,7 +416,7 @@ The following example specifies that related tasks should be returned in ascendi
 > [!NOTE]
 > - Nested `$expand` options can only be applied to single-valued navigation properties.
 >
-> - Each request can include a maximum of 10 `$expand` options. There is no limit on the depth of nested `$expand` options, but the limit of 10 total `$expand` options applies to these as well.
+> - Each request can include a maximum of 15 `$expand` options. There is no limit on the depth of nested `$expand` options, but the limit of 15 total `$expand` options applies to these as well.
 >
 > - This is a subset of the system query options described in the “11.2.4.2.1 Expand Options” section of [OData Version 4.0 Part 1: Protocol Plus Errata 02](https://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html). The options `$skip`, `$count`, `$search`, and `$levels` aren’t supported for the Web API.
 

powerapps-docs/developer/data-platform/webapi/retrieve-related-entities-query.md

@@ -1,7 +1,7 @@
 ---
 title: "Retrieve related table records with a query (Microsoft Dataverse)| Microsoft Docs"
 description: "Read how you can retrieve related table records by expanding the navigation properties."
-ms.date: 04/06/2022
+ms.date: 06/03/2022
 author: divka78
 ms.author: dikamath
 ms.reviewer: jdaly
@@ -28,7 +28,7 @@ Use the `$expand` system query option in the navigation properties to control wh
 If you include only the name of the navigation property, you’ll receive all the properties for related records. You can limit the properties returned for related records using the `$select` system query option in parentheses after the navigation property name. Use this for both single-valued and collection-valued navigation properties.  
 
 > [!NOTE]
->  - You are limited to no more than 10 `$expand` options in a query. This is to protect performance. Each `$expand` options creates a join that can impact performance. 
+>  - You are limited to no more than 15 `$expand` options in a query. This is to protect performance. Each `$expand` options creates a join that can impact performance. 
 >  - To retrieve related entities for an entity instance, see [Retrieve related tables for a table by expanding navigation properties](retrieve-entity-using-web-api.md#bkmk_expandRelated). 
 > - Queries which expand collection-valued navigation properties may return cached data for those properties that doesn’t reflect recent changes. It is recommended to use `If-None-Match` header with value `null` to override browser caching. See [HTTP Headers](compose-http-requests-handle-errors.md#bkmk_headers) for more details.
 > 
@@ -130,7 +130,7 @@ OData-Version: 4.0
 You can expand single-valued navigation properties to multiple levels by nesting an `$expand` option within another `$expand` option.
 
 > [!NOTE]
-> There is no limit on the depth of nested `$expand` options, but the combined limit of 10 total `$expand` options in a query still applies.
+> There is no limit on the depth of nested `$expand` options, but the combined limit of 15 total `$expand` options in a query still applies.
 
 The following query returns `task` records and expands the related `contact`, the `account` related to the `contact`, and finally to the `systemuser` who created the  `account` record.