Delta Payload The non-format specific aspects of the delta handling are described in the section Changes” “Requesting in . Responses Responses from a delta request are returned as a JSON object. The JSON object MUST contain an array-valued property named value containing all , , or , as well as or between entities, and MAY contain additional, unchanged entities. If the response contains a partial list of changes, it MUST include a for the client to retrieve the next set of changes. The last page of a delta response SHOULD contain a for retrieving subsequent changes once the current set of changes has been applied to the initial set. If the response from the delta link contains a count annotation, the returned number MUST include all added, changed, or deleted entities to be returned, as well as added or deleted links. Example : a 4.01 response with five changes, in order of occurrence for customer was changed to "Susan Halvenstern" ContactName Order 10643 was removed from customer 'ALFKI' Order 10645 was added to customer 'BOTTM' The shipping information for order 10643 was updated Customer 'ANTON' was deleted { "@context":"http://host/service/$metadata#Customers/$delta", "@count":5, "value": [ { "@id":"Customers('BOTTM')", "ContactName":"Susan Halvenstern" }, { "@context":"#Customers/$deletedLink", "source":"Customers('ALFKI')", "relationship":"Orders", "target":"Orders(10643)" }, { "@context":"#Customers/$link", "source":"Customers('BOTTM')", "relationship":"Orders", "target":"Orders(10645)" }, { "@context":"#Orders/$entity", "@id":"Orders(10643)", "ShippingAddress":{ "Street":"23 Tsawassen Blvd.", "City":"Tsawassen", "Region":"BC", "PostalCode":"T2F 8M4" }, }, { "@context":"#Customers/$deletedEntity", "@removed": {
Delta Payload The non-format specific aspects of the delta handling are described in the section “Requesting Changes” in . Responses Responses from a delta request are returned as a JSON object. The JSON object MUST contain an array-valued property named value containing all , , or , as well as or between entities, and MAY contain additional, unchanged entities. If the response contains a partial list of changes, it MUST include a for the client to retrieve the next set of changes. The last page of a delta response SHOULD contain a for retrieving subsequent changes once the current set of changes has been applied to the initial set. If the response from the delta link contains a count annotation, the returned number MUST include all added, changed, or deleted entities to be returned, as well as added or deleted links. Example : a 4.01 response with five changes, in order of occurrence ContactName for customer was changed to "Susan Halvenstern" Order 10643 was removed from customer 'ALFKI' Order 10645 was added to customer 'BOTTM' The shipping information for order 10643 was updated Customer 'ANTON' was deleted { "@context":"http://host/service/$metadata#Customers/$delta", "@count":5, "value": [ { "@id":"Customers('BOTTM')", "ContactName":"Susan Halvenstern" }, { "@context":"#Customers/$deletedLink", "source":"Customers('ALFKI')", "relationship":"Orders", "target":"Orders(10643)" }, { "@context":"#Customers/$link", "source":"Customers('BOTTM')", "relationship":"Orders", "target":"Orders(10645)" }, { "@context":"#Orders/$entity", "@id":"Orders(10643)", "ShippingAddress":{ "Street":"23 Tsawassen Blvd.", "City":"Tsawassen", "Region":"BC", "PostalCode":"T2F 8M4" }, }, { "@context":"#Customers/$deletedEntity", "@removed": {
odata-json-format-v4.01-cs01.docx