Metadata API Developer Guide
jNewer Version Available
Territory2Type
File Suffix and Directory Location
Territory2Type components have the suffix territory2Type and are stored in the territory2Types folder.
Version
Territory2Type components are available in API version 32.0 and later.
Special Access Rules
The Manage Territories permission is required for the deploy() operation, but not retrieve(). The retrieve() operation retrieves all the Territory2Type components in the org.
Fields
| Field Name | Field Type | Description |
|---|---|---|
| description | string | A description of the territory type. |
| name | string | Required. The user interface label for the territory type. |
| priority | int | Required. Used for Filter-Based Opportunity Territory Assignment (Pilot in Spring ’15 / Metadata API version 33). Lets you specify a priority for a territory type. For opportunity assignments, the filter examines all territories assigned to the account that the opportunity is assigned to. The account-assigned territory whose territory type priority is highest is then assigned to the opportunity. The priority field value on each territory type must be unique. Further, if there are multiple territories with the same territory type, and therefore the same priority, assigned to the account, no territory is not assigned to the opportunity. |
Declarative Metadata Sample Definition
The following example shows the definition of a Territory2Type component.
1<?xml version="1.0" encoding="UTF-8"?>
2<Territory2Type xmlns="http://soap.sforce.com/2006/04/metadata">
3 <name>Geo</name>
4 <description>Geographic allocation</description>
5</Territory2Type>Usage
Territory Management 2.0 components don’t support packaging or change sets and aren’t supported in CRUD calls.
Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.