Territory2Type Metadata Type in SFDX

Architectural Overview#

The Territory2Type metadata type represents the classification schema that categorizes and ranks territory nodes within Enterprise Territory Management (ETM / Territory2). In sophisticated global enterprises, sales structures comprise diverse operational tiers—such as Strategic Named Accounts, Commercial Mid-Market, High-Velocity Inside Sales, Government/Public Sector, and Channel Partner territories.

Architecturally, Territory2Type serves as a mandatory prerequisite for creating any Territory2 record. Beyond mere categorical labeling, each territory type possesses a numerical priority value. This priority indicates the relative weight and seniority of the territory classification across reporting views and helps sales leaders analyze revenue coverage across distinct organizational tiers. Deploying territory types as code guarantees structural consistency across development sandboxes and production environments.

Directory and File Conventions#

In SFDX source format, Territory2Type metadata files are maintained in the territory2Types directory:

Key Metadata Fields#

The Territory2Type metadata schema provides classification attributes, labels, and prioritization numbers:

Declarative XML and Package Manifest Examples#

Below is a declarative Territory2Type component defining a Strategic Accounts territory type with a high priority weighting:

<?xml version="1.0" encoding="UTF-8"?>
<Territory2Type xmlns="http://soap.sforce.com/2006/04/metadata">
    <name>Strategic Accounts</name>
    <description>Top tier global accounts with dedicated cross-functional account teams.</description>
    <priority>100</priority>
</Territory2Type>

Add the component to the package manifest:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Strategic_Accounts</members>
        <name>Territory2Type</name>
    </types>
    <version>68.0</version>
</Package>

Retrieval and Deployment#

Use modern Salesforce CLI commands to manage territory types:

# Retrieve all territory types
sf project retrieve start --metadata "Territory2Type:*"

# Deploy territory type to target sandbox
sf project deploy start --metadata "Territory2Type:Strategic_Accounts" --target-org uat

# Query territory types via Tooling API
sf data query --query "SELECT Id, DeveloperName, MasterLabel, Priority FROM Territory2Type" --use-tooling-api

Senior Architect Considerations#

1. Priority Numbering Schemes: Establish a standardized integer scale (e.g., 100 for Global Enterprise, 50 for Mid-Market, 10 for Velocity) to allow future intermediate tiers to be introduced without re-indexing existing priorities.
2. Type Immutability: Deleting a Territory2Type in an active environment is blocked by the platform if any active or planning Territory2 records reference it.
3. Packaging Strategy: Include Territory2Type definitions in your core foundational sales metadata package, decoupled from specific fiscal year models.

Frequently asked questions

What is the role of Territory2Type in Salesforce?

Territory2Type classifies individual Territory2 nodes by category and assigns a priority weight to help organize territory structures.

Which folder stores Territory2Type files in SFDX?

They are stored in force-app/main/default/territory2Types with the .territory2Type-meta.xml or .territory2Type file extension.

Why must Territory2Type be deployed before Territory2?

Every Territory2 component strictly requires a valid territory2Type reference; deploying territories without types causes reference failures.

What is the significance of the priority field on Territory2Type?

The priority integer defines the relative hierarchy or importance of the territory type when comparing different territory classifications.