---
schema_version: "1"
id: 60febaf3106766ef2c3661a358b961b1af51e10ef22fb59ad7d6349491b3c1a9
title: Bulk API Behavior for Data Cloud Sources in Territory Planning
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/sales_planning_data_cloud_bulk_api.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_planning_data_cloud_bulk_api.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 239375615d4c53c39554241fe0bb00b8d0455677f11ba1169cef276ace2358c0
description: Territory Planning uses a combination of Apex, REST, and Bulk API calls based on your Data Management settings. Use this reference to understand when Bulk API applies to Data Cloud sources and how to estimate the storage that your plans consume.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Bulk API Behavior for Data Cloud Sources in Territory Planning

Territory Planning uses a combination of Apex, REST, and Bulk API calls based on your Data Management settings. Use this reference to understand when Bulk API applies to Data Cloud sources and how to estimate the storage that your plans consume.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with <a href="https://help.salesforce.com/s/articleView?id=sales.territory_planning_api_access.htm&amp;type=5&amp;language=en_US" target="_blank">Web Services API enabled</a></td></tr></tbody></table>

## When Bulk API Applies

  
| Action | Bulk API Applies? | Details |
| --- | --- | --- |
| Dataset creation | Yes (conditional) | Applies when you build asynchronous datasets from object queries or territory model queries. |
| Cloning or refresh | Yes (conditional) | Applies when you clone or refresh asynchronous datasets that are derived from queries. |
| Alignment | Yes | Always applies when you build alignments, regardless of the data source. |
| Synchronous builds | No | Doesn't apply to synchronous dataset building or cloning. |
| Reports | No | Reports use the Report API even when the Bulk API setting is on. |

Bulk API avoids timeouts, but it can increase processing time. Bulk API is generally slower for datasets with fewer than 50,000 records.

## Storage Estimates

Sales Planning creates copies of records so that you simulate plans without affecting production data. Estimate storage as follows.

  
| Item | Storage | Notes |
| --- | --- | --- |
| Per dataset | 1 row per record | Sales Planning stores 1 row in Salesforce for each record that you bring into the planning scenario. |
| Per alignment | 1 row per record, plus 1 row per container | Storage includes 1 row for each record in the dataset and 1 row for each container, such as a postal code, that you add to the alignment. |

To free up storage, delete datasets and alignments that you no longer need, for example after you publish results back to your CRM.

#### See Also

- [Data Cloud Data Sources in Sales Planning](https://help.salesforce.com/s/articleView?id=sales.data_sources_management_data_cloud_sources.htm&release=264.0.0&type=5 "Build sales plans on Data Cloud Data Model Objects (DMOs) and Data Lake Objects (DLOs) in addition to CRM Analytics Data Pipeline datasets. Data Cloud is the foundational data platform across Salesforce, so you reuse data that your org already manages and scale beyond the license limits of Data Pipeline.")