Knowledge Center

Knowledge Center > Commerce > Zuora 360 > Zuora 360 Syncs and Salesforce Limits

Zuora 360 Syncs and Salesforce Limits

This article describes how Zuora 360 Syncs consume the Salesforce APIs and Bulk APIs. Use the information presented to plan your sync sessions so that you do not exceed the Salesforce API limits or Bulk API limits.

Salesforce Limits

This section summarizes the Salesforce limits that Zuora for Salesforce users should consider when planning and performing Zuora 360 Syncs.

Zuora for Salesforce packages are Salesforce certified managed packages with the Aloha App status. However, this package status does not effect the Salesforce API limits.

API-Based Sync

For Salesforce Professional and Enterprise, each organization has a limit of 1,000 API calls per user license per day. Review the limits for your Salesforce edition in Salesforce API Limit.

Each API-based Sync, such as On-demand Sync or Real-time Sync, consumes:

  • 4 to 8 API calls based on the number of object types that need to be synced
  • 1 API call per 200 records

Turbo Sync

Salesforce allows 5,000 Bulk API batches per user license per day. 

Each Turbo Sync, such as Manual Sync or Scheduled Sync, session consumes:

  • 1 Bulk API batch per every 9000 records of each object type to be DELETED
  • 1 Bulk API batch per every 9000 records of each object type to be UPSERTED

Salesforce API Limits and API-Based Sync

When you perform a API-based sync, such as On-demand or Real-time Sync, the sync session consumes Salesforce API calls. Use the usage information in the above Salesforce Limits section to plan your sync sessions so that you do not exceed your API limit. See Real-Time Sync for detailed information about how the Real-time Sync trigger setting affects the API consumption.

For example:

If a sync session has 1000 billing accounts, 1000 subscriptions, 1000 subscription components, and 1000 invoices to be synchronized, the session will consume approximately 28 API calls:

  • Basic overhead: 8 calls
  • 1000 billing accounts: ceil (1000/200) = 5 calls
  • 1000 subscriptions: ceil (1000/200) = 5 calls
  • 1000 subscription components: ceil (1000/200) = 5 calls
  • 1000 invoices: ceil (1000/200) = 5 calls
  • Total: 8 + 5 + 5 + 5 + 5 = 28 API calls

If an On-demand sync session has 1 billing account to sync, the session will consume 5 calls:

  • Basic overhead: 4 calls
  • 1 billing account: ceil (1/200) = 1 call
  • Total: 4 + 1 = 5 calls

Salesforce Bulk API Limits and Turbo Sync

When you perform a Turbo Sync, such as Manual Sync or Scheduled Sync, the sync session consumes Salesforce Bulk API batches. Use the usage information in the above Salesforce Limits section to plan your sync sessions so that you do not exceed your Bulk API limits. 

​​For example:

If a sync session has 1000 billing accounts, 5000 subscriptions, and 20000 subscription charges to be upserted, and 2000 subscription and 8000 subscription charges to be deleted, the sync session will consume the 7 Bulk API batches:

  • Upsert 1,000 billing accounts: ceil (1000 / 9000) = 1 batch
  • Upsert 5,000 subscriptions: ceil (5000 / 9000) = 1 batch
  • Upsert 20,000 subscription charges: ceil (20000/ 9000) = 3 batches
  • Delete 2,000 subscriptions: ceil (2000 / 9000) = 1 batch
  • Delete 8,000 subscription charges: ceil (2000 / 9000) = 1 batch
  • Total: 1 + 1 + 3 + 1 + 1 = 7 Bulk API batches
Last modified
17:12, 17 Feb 2016

Tags

Classifications

(not set)