Merge branch 'main' into phecke-entity-ref

Author: phecke

powerapps-docs/developer/data-platform/webapi/associate-disassociate-entities-using-web-api.md

@@ -271,7 +271,7 @@ The following example shows how to associate multiple existing [ActivityParty](.
 **Request:**
 
 ```HTTP
-PUT [Organization URI]/api/data/v9.0/emails(2479d20d-3a39-e711-8145-e0071b6a2001)/email_activity_parties
+PUT [Organization URI]/api/data/v9.2/emails(2479d20d-3a39-e711-8145-e0071b6a2001)/email_activity_parties
 Content-Type: application/json  
 Accept: application/json  
 OData-MaxVersion: 4.0  

powerapps-docs/developer/data-platform/webapi/compose-http-requests-handle-errors.md

@@ -2,7 +2,7 @@
 title: Compose HTTP requests and handle errors
 description: Learn about the HTTP methods and headers that form a part of HTTP requests for the Web API and how to identify and handle errors returned in the response.
 ms.topic: how-to
-ms.date: 09/26/2023
+ms.date: 08/29/2024
 author: MicroSri
 ms.author: sriknair
 ms.reviewer: jdaly
@@ -51,6 +51,12 @@ Protocol + Environment Name + Region + Base URL + Web API path + Version + Resou
 
 The maximum length of URL accepted by is 32 KB (32768 characters). This should be adequate for most kinds of request except certain `GET` operations which require very long string query parameters, such as queries using FetchXml. If you send requests inside the body of a `$batch` request, you can send requests with URLs up to 64 KB (65,536 characters). [Learn more about sending FetchXml within a $batch request](../fetchxml/retrieve-data.md#use-fetchxml-within-a-batch-request).
 
+### Maximum OData segment length
+
+The maximum length of any individual segment in an OData request cannot be longer than 260 characters. If a single segment of the OData request is more than 260 characters in length, then this can result in `400 Bad Request - Invalid URL`. The segment is the 'Resource' part of the url as described above and includes all characters needed to describe the endpoint and any inline parameters.
+
+For example, if the request is  `api/data/v9.2/MyApi(MyParameter='longvalue')`, `MyApi(MyParameter='longvalue')` is the segment that cannot exceed 260 characters. We recommend that you always use parameter aliases with OData functions. For example, composing your function as `/api/data/v9.2/MyApi(MyParameter=@alias)?@alias='longvalue'` shortens the segment to just `MyApi(MyParameter=@alias)`. [Learn more about using parameter aliases with Web API functions](use-web-api-functions.md#passing-parameters-to-a-function)
+
 <a name="version_compatiblity"></a>
 
 ### Version compatibility
@@ -238,7 +244,7 @@ When this plug-in is registered on the Create message of an account entity, and
 **Request:**
 
 ```http
-POST https://yourorg.api.crm.dynamics.com/api/data/v9.1/accounts HTTP/1.1
+POST https://yourorg.api.crm.dynamics.com/api/data/v9.2/accounts HTTP/1.1
 Content-Type: application/json;
 Prefer: odata.include-annotations="*"
 {

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

@@ -32,7 +32,7 @@ Use a `POST` request to send data to create a table row (entity record). You can
 
 ```http
 
-POST [Organization URI]/api/data/v9.0/accounts
+POST [Organization URI]/api/data/v9.2/accounts
 Content-Type: application/json; charset=utf-8
 OData-MaxVersion: 4.0
 OData-Version: 4.0
@@ -54,7 +54,7 @@ Accept: application/json
 
 HTTP/1.1 204 No Content
 OData-Version: 4.0
-OData-EntityId: [Organization URI]/api/data/v9.0/accounts(7eb682f1-ca75-e511-80d4-00155d2a68d1)
+OData-EntityId: [Organization URI]/api/data/v9.2/accounts(7eb682f1-ca75-e511-80d4-00155d2a68d1)
 
 ```
 
@@ -84,7 +84,7 @@ This example creates a new account entity and returns the requested data in the
 
  ```http
 
-POST [Organization URI]/api/data/v9.0/accounts?$select=name,creditonhold,address1_latitude,description,revenue,accountcategorycode,createdon
+POST [Organization URI]/api/data/v9.2/accounts?$select=name,creditonhold,address1_latitude,description,revenue,accountcategorycode,createdon
 OData-MaxVersion: 4.0
 OData-Version: 4.0
 Accept: application/json
@@ -111,7 +111,7 @@ Preference-Applied: return=representation
 OData-Version: 4.0
 
 {
-    "@odata.context": "[Organization URI]/api/data/v9.0/$metadata#accounts/$entity",
+    "@odata.context": "[Organization URI]/api/data/v9.2/$metadata#accounts/$entity",
     "@odata.etag": "W/\"536530\"",
     "accountid": "d6f193fc-ce85-e611-80d8-00155d2a68de",
     "accountcategorycode": 1,
@@ -158,7 +158,7 @@ More information:
 **Request:**
 
 ```http
-POST [Organization URI]/api/data/v9.0/accounts
+POST [Organization URI]/api/data/v9.2/accounts
 Content-Type: application/json; charset=utf-8
 OData-MaxVersion: 4.0
 OData-Version: 4.0
@@ -191,7 +191,7 @@ Accept: application/json
 
 HTTP/1.1 204 No Content
 OData-Version: 4.0
-OData-EntityId: [Organization URI]/api/data/v9.0/accounts(3c6e4b5f-86f6-e411-80dd-00155d2a68cb)
+OData-EntityId: [Organization URI]/api/data/v9.2/accounts(3c6e4b5f-86f6-e411-80dd-00155d2a68cb)
 
 ```
 
@@ -209,7 +209,7 @@ This request is using the `Prefer: return=representation` header so it returns t
 
 ```http
 
-POST [Organization URI]/api/data/v9.0/accounts?$select=name&$expand=primarycontactid($select=fullname),Account_Tasks($select=subject)
+POST [Organization URI]/api/data/v9.2/accounts?$select=name&$expand=primarycontactid($select=fullname),Account_Tasks($select=subject)
 Content-Type: application/json; charset=utf-8
 OData-MaxVersion: 4.0
 OData-Version: 4.0
@@ -236,7 +236,7 @@ OData-Version: 4.0
 Preference-Applied: return=representation
 
 {
-    "@odata.context": "[Organization URI]/api/data/v9.1/$metadata#accounts(name,primarycontactid(fullname),Account_Tasks(subject))/$entity",
+    "@odata.context": "[Organization URI]/api/data/v9.2/$metadata#accounts(name,primarycontactid(fullname),Account_Tasks(subject))/$entity",
     "@odata.etag": "W/\"36236432\"",
     "name": "Sample Account",
     "accountid": "00000000-0000-0000-0000-000000000004",
@@ -289,7 +289,7 @@ Use the [InitializeFrom function](xref:Microsoft.Dynamics.CRM.InitializeFrom) to
 
 To determine whether two entities can be mapped, use the following query:
 
-`GET [Organization URI]/api/data/v9.1/entitymaps?$select=sourceentityname,targetentityname&$orderby=sourceentityname`
+`GET [Organization URI]/api/data/v9.2/entitymaps?$select=sourceentityname,targetentityname&$orderby=sourceentityname`
 
 Creating a new record from another record is a two-step process. First, use the `InitializeFrom` function to return property values mapped from the original record. Then, combine the response data returned in the `InitializeFrom` function with any changes you want to make and then `POST` the data to create the record.
 
@@ -300,7 +300,7 @@ The following example shows how to create an account record using the values of
 **Request:**
 
 ```http
-GET [Organization URI]/api/data/v9.0/InitializeFrom(EntityMoniker=@p1,TargetEntityName=@p2,TargetFieldType=@p3)?@p1={'@odata.id':'accounts(00000000-0000-0000-0000-000000000001)'}&@p2='account'&@p3=Microsoft.Dynamics.CRM.TargetFieldType'ValidForCreate'
+GET [Organization URI]/api/data/v9.2/InitializeFrom(EntityMoniker=@p1,TargetEntityName=@p2,TargetFieldType=@p3)?@p1={'@odata.id':'accounts(00000000-0000-0000-0000-000000000001)'}&@p2='account'&@p3=Microsoft.Dynamics.CRM.TargetFieldType'ValidForCreate'
 If-None-Match: null
 OData-Version: 4.0
 OData-MaxVersion: 4.0
@@ -312,7 +312,7 @@ Accept: application/json
 
 ```json
 {
-    "@odata.context": "[Organization URI]/api/data/v9.0/$metadata#accounts/$entity",
+    "@odata.context": "[Organization URI]/api/data/v9.2/$metadata#accounts/$entity",
     "@odata.type": "#Microsoft.Dynamics.CRM.account",
     "[email protected]": "accounts(00000000-0000-0000-0000-000000000001)",
     "[email protected]": "transactioncurrencies(732e87e1-1d96-e711-80e4-00155db75426)",
@@ -331,14 +331,14 @@ The response received from `InitializeFrom` function consists of values of mappe
 Other property values can also be set and/or modified for the new record by adding them in the JSON request body, as shown in the following example:
 
 ```http
-POST [Organization URI]/api/data/v9.0/accounts
+POST [Organization URI]/api/data/v9.2/accounts
 Content-Type: application/json; charset=utf-8
 OData-MaxVersion: 4.0
 OData-Version: 4.0
 Accept: application/json
 
     {
-        "@odata.context": "[Organization URI]/api/data/v9.0/$metadata#accounts/$entity",
+        "@odata.context": "[Organization URI]/api/data/v9.2/$metadata#accounts/$entity",
         "@odata.type": "#Microsoft.Dynamics.CRM.account",
         "[email protected]": "accounts(00000000-0000-0000-0000-000000000001)",
         "[email protected]": "transactioncurrencies(732e87e1-1d96-e711-80e4-00155db75426)",

powerapps-docs/developer/data-platform/webapi/impersonate-another-user-web-api.md

@@ -42,7 +42,7 @@ There are two ways you can impersonate a user, both of which are made possible b
  **Request:**
 
 ```http 
-POST [Organization URI]/api/data/v9.0/accounts HTTP/1.1  
+POST [Organization URI]/api/data/v9.2/accounts HTTP/1.1  
 CallerObjectId: e39c5d16-675b-48d1-8e67-667427e9c084  
 Accept: application/json  
 Content-Type: application/json; charset=utf-8  
@@ -57,7 +57,7 @@ OData-Version: 4.0
 ```http 
 HTTP/1.1 204 No Content  
 OData-Version: 4.0  
-OData-EntityId: [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-000000000003)  
+OData-EntityId: [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-000000000003)  
 ```  
 
 <a name="bkmk_Determinetheactualuser"></a>
@@ -69,7 +69,7 @@ When an operation such as creating an entity is performed using impersonation, y
  **Request:**
 
 ```http
-GET [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-000000000003)?$select=name&$expand=createdby($select=fullname),createdonbehalfby($select=fullname),owninguser($select=fullname) HTTP/1.1   
+GET [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-000000000003)?$select=name&$expand=createdby($select=fullname),createdonbehalfby($select=fullname),owninguser($select=fullname) HTTP/1.1   
 Accept: application/json  
 OData-MaxVersion: 4.0  
 OData-Version: 4.0  
@@ -83,7 +83,7 @@ Content-Type: application/json; odata.metadata=minimal
 ETag: W/"506868"  
   
 {
-  "@odata.context": "[Organization URI]/api/data/v9.0/$metadata#accounts(name,createdby(fullname,azureactivedirectoryobjectid),createdonbehalfby(fullname,azureactivedirectoryobjectid),owninguser(fullname,azureactivedirectoryobjectid))/$entity",
+  "@odata.context": "[Organization URI]/api/data/v9.2/$metadata#accounts(name,createdby(fullname,azureactivedirectoryobjectid),createdonbehalfby(fullname,azureactivedirectoryobjectid),owninguser(fullname,azureactivedirectoryobjectid))/$entity",
   "@odata.etag": "W/\"2751197\"",
   "name": "Sample Account created using impersonation",
   "accountid": "00000000-0000-0000-000000000003",

powerapps-docs/developer/data-platform/webapi/manage-duplicate-detection-create-update.md

@@ -39,7 +39,7 @@ The following example shows how to detect duplicates during `Create` and `Update
 **Request:**
 
 ```http
-POST [Organization URI]/org1/api/data/v9.0/leads HTTP/1.1
+POST [Organization URI]/org1/api/data/v9.2/leads HTTP/1.1
 If-None-Match: null
 OData-Version: 4.0
 OData-MaxVersion: 4.0
@@ -86,7 +86,7 @@ The example shown below attempts to update an existing lead entity record which
 **Request:**
 
 ```http
-PATCH [Organization URI]/api/data/v9.0/leads(c4567bb6-47a3-e711-811b-e0071b6ac1b1) HTTP/1.1
+PATCH [Organization URI]/api/data/v9.2/leads(c4567bb6-47a3-e711-811b-e0071b6ac1b1) HTTP/1.1
 If-None-Match: null
 OData-Version: 4.0
 OData-MaxVersion: 4.0

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

@@ -1,7 +1,7 @@
 ---
 title: "Merge table rows using the Web API (Microsoft Dataverse)| Microsoft Docs"
 description: "Read how to use the Merge unbound action to merge two table rows"
-ms.date: 08/10/2023
+ms.date: 08/30/2024
 author: MicroSri
 ms.author: sriknair
 ms.reviewer: jdaly
@@ -15,7 +15,7 @@ contributors:
 
 [!INCLUDE[cc-terminology](../includes/cc-terminology.md)]
 
-When you find duplicate records you can combine them into one using the <xref:Microsoft.Dynamics.CRM.Merge?text=Merge Action>.
+When you find duplicate records, you can combine them into one using the [Merge Action](xref:Microsoft.Dynamics.CRM.Merge).
 
 > [!NOTE]
 > Only the following entity types can be merged:
@@ -34,19 +34,19 @@ Merge is an unbound action that accepts four parameters:
 |---------|---------|---------|---------|
 |`Target`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|The target of the merge operation.| No|
 |`Subordinate`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|The entity record from which to merge data.| No|
-|`UpdateContent`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|Additional entity attributes to be set during the merge operation.| Yes|
+|`UpdateContent`|<xref:Microsoft.Dynamics.CRM.crmbaseentity>|More entity attributes to be set during the merge operation.| Yes|
 |`PerformParentingChecks`|Boolean|Indicates whether to check if the parent information is different for the two entity records.| No|
 
-Merging will move any useful data from the `Subordinate` record to the `Target` record. Any existing data in the `Target` record will not be overwritten. Then the `Subordinate` record is deactivated.
-To perform this operation the caller must have privileges and access rights to both the records identified as the `Target` and `Subordinate`.
+Merging moves any useful data from the `Subordinate` record to the `Target` record. Any existing data in the `Target` record aren't overwritten. Then the `Subordinate` record is deactivated.
+To perform this operation, the caller must have privileges and access rights to both the records identified as the `Target` and `Subordinate`.
 
 Use a POST request to send data to merge records. 
 This example merges two account entity records while updating `accountnumber` property of the record that will remain after the merge.
 
 **Request:**
 
 ```http
-POST [Organization URI]/api/data/v9.0/Merge HTTP/1.1
+POST [Organization URI]/api/data/v9.2/Merge HTTP/1.1
 Content-Type: application/json; charset=utf-8
 OData-MaxVersion: 4.0
 OData-Version: 4.0
@@ -85,18 +85,18 @@ OData-Version: 4.0
 
 The merge behavior for `incident` (case) table is different from `account`, `contact`, or `lead` tables.
 
-- The `UpdateContent` parameter data is not used.
+- The `UpdateContent` parameter data isn't used.
 - Merge is performed in the security context of the user
 
-   Merge operations for other tables are performed with a system user security context. Because incident merge operations are performed in the security context of the user, the user must have the security privileges to perform any of the actions, such as re-parenting related records, that are performed by the merge operation.
+   Merge operations for other tables are performed with a system user security context. Because incident merge operations are performed in the security context of the user, the user must have the security privileges to perform any of the actions, such as reparenting related records, that the merge operation performs.
 
-   If the user merging records doesn't have privileges for all the actions contained within the merge operation, the merge operation will fail and roll back to the original state.
+   If the user merging records doesn't have privileges for all the actions contained within the merge operation, the merge operation fail and roll back to the original state.
 
 ### See also
 
 [Use Web API actions](use-web-api-actions.md)<br />
 [Merge duplicate records](../../../user/merge-duplicate-records.md)<br />
-<xref:Microsoft.Crm.Sdk.Messages.MergeRequest?text=MergeRequest Class><br />
+[MergeRequest Class](xref:Microsoft.Crm.Sdk.Messages.MergeRequest)<br />
 [Administration Guide: Merge data](/power-platform/admin/merge-data)<br />
 [Dynamics 365 for Service: Merge cases](/dynamics365/customer-service/customer-service-hub-user-guide-merge-cases)
 

powerapps-docs/developer/data-platform/webapi/multitable-lookup.md

@@ -168,7 +168,7 @@ The following JSON is the body of the response from the HTTP `POST` request cont
 ```json
 {
     "@odata.context":
-      "http://<organization URL>/api/data/v9.1/$metadata#Microsoft.Dynamics.CRM.CreatePolymorphicLookupAttributeResponse",
+      "http://<organization URL>/api/data/v9.2/$metadata#Microsoft.Dynamics.CRM.CreatePolymorphicLookupAttributeResponse",
 
     "RelationshipIds":[
         "77d4c6e9-0397-eb11-a81c-000d3a6cfaba",
@@ -203,7 +203,7 @@ The following table lists the operations relevant for table and attribute data.
 The following example request that creates a new record with two rows.   
 
 ```http
-POST [OrganizationUrl]/api/data/v9.1/new_checkouts
+POST [OrganizationUrl]/api/data/v9.2/new_checkouts
 ```
 
 ```http

powerapps-docs/developer/data-platform/webapi/overview.md

@@ -1,7 +1,7 @@
 ---
 title: "Use the Microsoft Dataverse Web API (Dataverse)| Microsoft Docs"
 description: "The Microsoft Dataverse Web API implements the OData v4 protocol and provides a development experience that can be used across a wide variety of programming languages, platforms, and devices"
-ms.date: 06/20/2023
+ms.date: 08/29/2024
 author: MicroSri
 ms.author: sriknair
 ms.reviewer: jdaly
@@ -32,7 +32,7 @@ The Web API allows you to do all the same operations as the SDK for .NET but pre
 
 Now that you have read an overview of the Web API, proceed to the [Get started with Dataverse Web API](get-started-dynamics-365-web-api-csharp.md) topic to learn how to write your first C# program in Visual Studio that uses the Web API.
 
-If you are a JavaScript developer and want to use the Web API in model-driven apps, navigate to [Client-side JavaScript using Web API in model-driven apps](get-started-web-api-client-side-javascript.md).
+If you are a JavaScript developer and want to use the Web API in model-driven apps, look at [Client-side JavaScript using Web API in model-driven apps](get-started-web-api-client-side-javascript.md).
 
 ### Related Sections
 

powerapps-docs/developer/data-platform/webapi/perform-conditional-operations-using-web-api.md

@@ -45,7 +45,7 @@ The following example message pair returns data for an account record with the `
  **Request:**
 
 ```http  
-GET [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-0000-000000000001)?$select=accountcategorycode,accountnumber,creditonhold,createdon,numberofemployees,name,revenue   HTTP/1.1  
+GET [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-0000-000000000001)?$select=accountcategorycode,accountnumber,creditonhold,createdon,numberofemployees,name,revenue   HTTP/1.1  
 Accept: application/json  
 OData-MaxVersion: 4.0  
 OData-Version: 4.0  
@@ -67,7 +67,7 @@ The following sections describe limitations to using conditional retrievals.
 Check if an table has optimistic concurrency enabled using the following Web API request. Tables that have optimistic concurrency enabled have [EntityMetadata.IsOptimisticConcurrencyEnabled](xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IsOptimisticConcurrencyEnabled) property set to `true`.
 
 ```http
-GET [Organization URI]/api/data/v9.0/EntityDefinitions(LogicalName='<Entity Logical Name>')?$select=IsOptimisticConcurrencyEnabled
+GET [Organization URI]/api/data/v9.2/EntityDefinitions(LogicalName='<Entity Logical Name>')?$select=IsOptimisticConcurrencyEnabled
 ```
 
 ### Query must not include $expand
@@ -95,7 +95,7 @@ If you're updating data and there's some possibility that the record was deleted
  **Request:**
 
 ```http  
-PATCH [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
+PATCH [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
 Content-Type: application/json  
 OData-MaxVersion: 4.0  
 OData-Version: 4.0  
@@ -137,7 +137,7 @@ If you're inserting data, there's some possibility that a record with the same `
  **Request:**
 
 ```http
-PATCH [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
+PATCH [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
 Content-Type: application/json  
 OData-MaxVersion: 4.0  
 OData-Version: 4.0  
@@ -184,7 +184,7 @@ The following delete request for an account with `accountid` of`00000000-0000-00
  **Request:**
 
 ```http  
-DELETE [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
+DELETE [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
 If-Match: W/"470867"  
 Accept: application/json  
 OData-MaxVersion: 4.0  
@@ -214,7 +214,7 @@ The following update request for an account with `accountid` of `00000000-0000-0
  **Request:**
 
 ```http  
-PATCH [Organization URI]/api/data/v9.0/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
+PATCH [Organization URI]/api/data/v9.2/accounts(00000000-0000-0000-0000-000000000001) HTTP/1.1  
 If-Match: W/"470867"  
 Accept: application/json  
 OData-MaxVersion: 4.0