Merge pull request #9229 from MicrosoftDocs/jdaly-main-link-entity-orders

reverse order for process link-entity orders

Author: JimDaly

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

@@ -57,9 +57,9 @@ If you want to use *descending* order, set the `descending` attribute to `true`.
 </fetch>
 ```
 
-## Process `link-entity` orders last
+## Process `link-entity` orders first
 
-Dataverse always orders attributes specified by the `link-entity` before attributes for the `entity` element.
+Dataverse always orders attributes specified by the `link-entity` after attributes for the `entity` element.
 
 The following example shows a conventional ordering pattern for both `link-entity` attributes and `entity` attributes.
 
@@ -76,20 +76,22 @@ The following example shows a conventional ordering pattern for both `link-entit
       alias='parentaccount'>
       <attribute name='name'
         alias='parentaccount' />
+        <!-- The link-entity parentaccount name -->
       <order attribute='name' />
     </link-entity>
+    <!-- The entity account name -->
     <order attribute='name' />
   </entity>
 </fetch>
 ```
 
 In this case, the results are ordered using following attributes:
 
-- First => `parentaccountname.name`
-- Last => `account.name`
+- First => `account.name`
+- Last => `parentaccountname.name`
 
 
-To ensure the `link-entity` order isn't applied first, move the `order` element from the `link-entity` element to the `entity` element and use the `entityname` attribute on the `order` element to refer to the `link-entity` `alias` value.
+To ensure the `link-entity` order is applied first, move the `order` element from the `link-entity` element to the `entity` element above the other `order` element, and use the `entityname` attribute on the `order` element to refer to the `link-entity` `alias` value.
 
 
 ```xml
@@ -106,17 +108,19 @@ To ensure the `link-entity` order isn't applied first, move the `order` element
       <attribute name='name'
         alias='parentaccount' />
     </link-entity>
-    <order attribute='name' />
+    <!-- The link-entity parentaccount name -->
     <order entityname='parentaccount'
       attribute='name' />
+      <!-- The entity account name -->
+    <order attribute='name' />
   </entity>
 </fetch>
 ```
 
 Now, the results are ordered using the following attributes:
 
-- First => `account.name`
-- Last => `parentaccount.name`
+- First => `parentaccount.name`
+- Last => `account.name`
 
 ## Ordering lookup and choice columns
 

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

@@ -46,7 +46,7 @@ This example return account records in ascending order by `createdon`, `name`, a
 |`attribute`|Yes|The `name` of the [attribute element](attribute.md) to sort the data by.|
 |`alias`|No|The `alias` of the [attribute element](attribute.md) to sort the data by|
 |`descending`|No|Whether to sort the data in descending order.|
-|`entityname`|No|Use this to specify sort order for `link-entity` elements so that they are not applied first. In an `order` within an `entity` element, set `entityname` to the  `alias` value of a `link-entity`. [Learn how to apply `link-entity` orders last](../order-rows.md#process-link-entity-orders-last)|
+|`entityname`|No|Use this attribute to specify sort order for `link-entity` elements so that they aren't applied last. In an `order` within an `entity` element, set `entityname` to the  `alias` value of a `link-entity`. [Learn how to apply `link-entity` orders first](../order-rows.md#process-link-entity-orders-first)|
 
 ## Parent elements