Batch Processing
With Web Services On Demand, you can perform batch operations that optimize performance by combining multiple requests into one.
Oracle CRM On Demand batch processing has a limit of 20 top-level records for each request and is supported for the following operations:
Insert
Delete
Update
InsertOrUpdate (Web Services v1.0 only)
Because batch calls take longer to process than single operations they must only be used in instances where longer response time would not impact the user experience. However, for such interactive applications, if Oracle CRM On Demand needs to process multiple records of the same type, batch operations increase the performance.
If a single record in a batch causes an error, the entire batch is not processed. For example, a batch of 20 Account inserts where one record contains an error will require all records to be reinserted.
A batch error could result from a data error or other error (for example, network outage, session expiry, and so on). If the error is not data-related, it is recommended that the user logs in again and tries the Web service call again. If the error is data-related, the batch can be split into smaller batches so that the records that do not cause errors can be processed.