---
schema_version: "1"
id: 2c9d03dd99adbcd3f093d270d4c01396df79815d34f01f25dd1f995c6fc161cd
title: Considerations, Allocations, and Guidelines for Planning Territories with Live Data
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_data_sets_live_data_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_data_sets_live_data_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 35682414f5b9040f0ea2b205f126f96517d20ebbf5fef2dbc114577cef4db31a
description: Prepare for planning territories with live Salesforce data and discover how it differs from copied data when you create datasets in Territory Planning.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Considerations, Allocations, and Guidelines for Planning Territories with Live Data

Prepare for planning territories with live Salesforce data and discover how it differs from copied data when you create datasets in Territory 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 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>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:29.325513196480934%">
        <col style="width:70.67448680351906%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49059e75">Goal</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49059e78">Details about Using Live Data</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Goal" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e75 ">Create and work with datasets and alignments</td>

          <td data-label="Details about Using Live Data" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e78 ">Whoever creates and works with live datasets and their alignments require access
            to all referenced fields within those datasets and alignments.</td>

        </tr>
        <tr class="">
          <td data-label="Goal" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e75 ">Add data sources to datasets</td>

          <td data-label="Details about Using Live Data" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e78 ">
            <p>Allocations and supported functions differ from copied data. Here’s how.</p>
            <ul>
              <li>Each report can include up to 50,000 records.</li>

              <li>Each query and segment can include up to 100,000 records.</li>

              <li>Each dataset can include up to 100,000 records.</li>

              <li>Territory models from Sales Territories aren’t available as a query data
                source.</li>

              <li>Aggregation for reports, queries, and segments isn’t available.</li>

              <li>You can add unit attributes, but can’t update existing unit attributes.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Goal" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e75 ">Plan territories on the map</td>

          <td data-label="Details about Using Live Data" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e78 ">
            <p>Map requirements and functions differ from copied data.</p>
            <ul>
              <li>Include latitude and longitude coordinates as attributes.</li>

              <li>If you plan territories with boundaries, set the postal code boundary type.
                Assignments rely on postal and country codes, instead of latitude and longitude
                coordinates.</li>

              <li>Specify up to five boundary sets per alignment.</li>

              <li>Live datasets don’t support using the analyze and compare function with
                non-geographic datasets.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Goal" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e75 ">Optimize performance when loading alignments</td>

          <td data-label="Details about Using Live Data" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e78 ">
            <p>The number of attributes you include and how you handle unassigned units affects performance.</p>
            <ul>
              <li>Alignments can include up to 20 attributes at a time with the option to exchange
                them for others.</li>

              <li>Alignments can require more time to load when you exclude unassigned units in
                alignments.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Goal" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e75 ">Publish territory plans</td>

          <td data-label="Details about Using Live Data" class="slds-cell-wrap" style="vertical-align:top;" headers="d49059e78 ">Publishing alignments to Sales Territories and CSV files doesn’t include point
            ZIP codes.</td>

        </tr>
      </tbody>
    </table>