You are here:
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.
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions with Web Services API enabled |
| 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.
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.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.