Update Batch

A batch of objects can be updated by issuing a PUT request to the appropriate application and table:

PUT /{application}/{table}

An input entity must be provided in JSON or XML as specified by the command’s content-type. The message has the same format as the Add Batch command with the following differences:

•	Object IDs: Every object in the batch must be assigned an ID. If the _ID field value is missing within a doc group, that update is skipped.

•	Nullifying SV scalars: An object’s SV scalar field can be set to null by giving it an empty value. Example:

<doc>

<field name="SendDate"></field>

...

</doc>

In JSON, the keyword NULL or an empty string (“”) can be assigned to nullify an SV scalar.

•	Removing MV field values: MV scalar and link values can be removed with a remove group. Example:

<doc>

<field name="Tags">

<remove>

<value>AfterHours</value>

</remove>

</field>

<field name="InternalRecipients">

<remove>

<value>Ii91O7qHb8rPhzvaihzTqw==</value>

</remove>

</field>

...

</doc>

Values can be added and removed for the same field in the same doc group.

If the PUT request is successful, a 200 OK response is returned with a batch-result group. It contains a doc element for each object updated, including _ID, status, and other elements as needed.

Updating an object is an idempotent operation: if an update does not actually change any of the object’s fields, the update is a no-op. Hence, performing the same update in succession is safe.