10,730
edits
Important: Deprecating old WebView — Publish failed error
Releases/Spring 2022: Difference between revisions
Jump to navigation
Jump to search
→Salesforce: Optimized upload of multiple records using Collections API
| Line 109: | Line 109: | ||
The ability to sync archived records is particularly useful for Events because Salesforce automatically archives them after one year. | The ability to sync archived records is particularly useful for Events because Salesforce automatically archives them after one year. | ||
== Salesforce: | == Salesforce: optimized upload of multiple records == | ||
We have changed the Salesforce API for uploading records. Instead of the [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_batch.htm Batch API], we are now using the newer [https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobjects_collections.htm Collections API]. This significantly saves [[API calls]] and improves upload speed if many (25+) records per entity are uploaded. | |||
== Route plan == | == Route plan == | ||