Composite Operations

[k-capehart]

Use Composite to allow users to group dependent calls into a single request

• https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/requests_composite.htm

Examples

• Create record with child records in same request
• Create record and retrieve record with ID in same request

Use Composite Batch to allow users to group independent requests together into a single request

• https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_batch.htm
• https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_composite_batch.htm#topic-title

Examples

• Perform an insert and then query in same request

Considerations

• There is still a limit of 25 subrequests (5 if they are SObject Collections)
• Use composite calls to optimize the collections functions
  • We could group batches together into composite requests
• I separated the logic between Collections and Composite functions because: with Composite you can insert a large amount of data with the AllOrNone parameter, while Batch and Collections have no limit to the number of batches but AllOrNone won't persist across the batches

[k-capehart]

Some composite operations are already available, as they were created alongside function intended for inserting, updating, etc sobject collections