Adding section on Maximum OData Segment length

Adding section on Maximum OData Segment length

Author: legunter

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

@@ -51,6 +51,10 @@ 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 paramters. i.e. for the request `api/data/v9.0/MyApi(MyParameter='longvalue')`, `MyApi(MyParameter='longvalue')` is the segment that cannot exceed 260 characters. One work around is to use parameter aliasing like `<org>/api/data/v9.0/MyApi(MyParameter=@alias)?@alias='longvalue'` which shortens the segment to just `MyApi(MyParameter=@alias)`. An alternate work around is to use the $batch API to pass the request. [Learn more about sending FetchXml within a $batch request](../fetchxml/retrieve-data.md#use-fetchxml-within-a-batch-request)
+
 <a name="version_compatiblity"></a>
 
 ### Version compatibility