Behavior of Service Data Object Attribute in Request Payload

This table lists the service data object attribute values in the request payload and describes how create and update operations process these values.

Request Payload Element Behavior In create Operation Behavior In update Operation
The service data object attribute is not included in the request payload. This is the absent element case. If a default value is defined, the new row is set to this value. The attribute value for the service data object is not updated.
The service data object attribute is included in the payload and has an empty element. For example, <attributeName/> and <attributeName></attributeName>. If the attribute is nillable, the value is set to nil. Otherwise it is an invalid input. If the attribute is nillable, the value is not updated. Otherwise it is an invalid input.
The service data object attribute value is included in the payload and has a nil value. For example, <attributeName xsi:nil="true">. If the attribute is nillable, the value is set to nil. Otherwise it is an invalid input. If the attribute is nillable, the value is updated to nil. Otherwise it is an invalid input.
The service data object attribute is included in the payload. It is not an empty element and contains a non-nil value. The service data object attribute is set to the specified value. The service data object attribute is updated to the specified value.
Related Topics
  • Service with Warnings Enabled Examples
  • find Operation Examples