---
schema_version: "1"
id: b760dc115f71e0c0071722492122a6a63f8907953c95c940239ee094930cd0b9
title: Considerations for Creating Datasets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/sales_planning_setup_prepare_datasets_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_planning_setup_prepare_datasets_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 09ce578ce71619d4d2649177fa13611daec797b04d61f54a436a0ad54d60ca95
description: Make sure that your datasets include data in the correct formats so that your planning processes run smoothly in Sales Planning.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Considerations for Creating Datasets

Make sure that your datasets include data in the correct formats so that your planning processes run smoothly in Sales Planning.

### 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 for an additional cost in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Sales Planning in English only, and only if you have Web Services API enabled</td></tr></tbody></table>

- To import records from CSV files, include record IDs as strings.
- Sales Planning doesn’t support live data connections from Salesforce.
- Datasets that you create in CRM Analytics within the Sales Planning app apply only to Sales Planning. Avoid using those datasets with other CRM Analytics dashboards.
- Before you add fields that include special characters in their API field names, remove those characters. For example, change `Owner.Name` to `OwnerName`.
- To carve territories in Territory Planning, include latitude and longitude coordinates as numeric values.
    
    To avoid problems with default precision settings, it’s best to set precision and scale to 15 and 12, respectively, directly within the Data Pipelines connection. If you plan to use copied data in Territory Planning, you can add latitude and longitude coordinates later.
- To carve territories from segments, confirm that you've enabled **Asynchronous Data Set Creation** in Territory Planning settings.