diff --git a/docs/odata-protocol/odata-protocol.html b/docs/odata-protocol/odata-protocol.html index 9f0a4dfa2..43142da93 100644 --- a/docs/odata-protocol/odata-protocol.html +++ b/docs/odata-protocol/odata-protocol.html @@ -1285,9 +1285,9 @@

Core.MediaType annotation (see OData-VocCore) if this annotation is present. If not annotated, the format cannot be predicted by the client.

The default format for Edm.Geo types is text/plain using the WKT (well-known text) format, see rules fullCollectionLiteral, fullLineStringLiteral, fullMultiPointLiteral, fullMultiLineStringLiteral, fullMultiPolygonLiteral, fullPointLiteral, and fullPolygonLiteral in OData-ABNF.

The default format for single primitive values except Edm.Binary and the Edm.Geo types is text/plain. Responses for type Edm.String can use the charset format parameter to specify the character set used for representing the string value. Responses for the other primitive types follow the rules booleanValue, byteValue, dateValue, dateTimeOffsetValue, decimalValue, doubleValue, durationValue, enumValue, guidValue, int16Value, int32Value, int64Value, sbyteValue, singleValue, and timeOfDayValue in OData-ABNF.

-

A $value request for a property or operation result that is null results in a 204 No Content response.

+

A raw value request for a property or operation result of type Edm.Stream returns 400 Bad Request.

+

A raw value request for a property or operation result that is null results in a 204 No Content response.

If the property or operation result is not available, for example due to permissions, the service responds with 404 Not Found.

-

Appending /$value to the URL of a property or operation result of type Edm.Stream returns 400 Bad Request.

Example 32:

GET http://host/service/Products(1)/Name/$value
diff --git a/docs/odata-protocol/odata-protocol.md b/docs/odata-protocol/odata-protocol.md index 7e6bc2153..ba1b94cc4 100644 --- a/docs/odata-protocol/odata-protocol.md +++ b/docs/odata-protocol/odata-protocol.md @@ -2795,15 +2795,15 @@ other primitive types follow the rules `booleanValue`, `byteValue`, `int64Value`, `sbyteValue`, `singleValue`, and `timeOfDayValue` in [OData-ABNF](#ODataABNF). -A `$value` request for a property or operation result that is `null` results in a +A raw value request for a property or operation result of type `Edm.Stream` +returns `400 Bad Request`. + +A raw value request for a property or operation result that is `null` results in a [`204 No Content`](#ResponseCode204NoContent) response. If the property or operation result is not available, for example due to permissions, the service responds with [`404 Not Found`](#ResponseCode404NotFound). -Appending `/$value` to the URL of a property or operation result of type `Edm.Stream` -returns `400 Bad Request`. - ::: example Example 32: ``` diff --git a/odata-protocol/11 Data Service Requests.md b/odata-protocol/11 Data Service Requests.md index 904600765..387cb0e32 100644 --- a/odata-protocol/11 Data Service Requests.md +++ b/odata-protocol/11 Data Service Requests.md @@ -269,15 +269,15 @@ other primitive types follow the rules `booleanValue`, `byteValue`, `int64Value`, `sbyteValue`, `singleValue`, and `timeOfDayValue` in [OData-ABNF](#ODataABNF). -A `$value` request for a property or operation result that is `null` results in a +A raw value request for a property or operation result of type `Edm.Stream` +returns `400 Bad Request`. + +A raw value request for a property or operation result that is `null` results in a [`204 No Content`](#ResponseCode204NoContent) response. If the property or operation result is not available, for example due to permissions, the service responds with [`404 Not Found`](#ResponseCode404NotFound). -Appending `/$value` to the URL of a property or operation result of type `Edm.Stream` -returns `400 Bad Request`. - ::: example Example ##ex: ```