Considerations for Custom Area Fields in Territory Planning

Required Fields

If you add a required field to the Territory Planning Area object, Territory Planning fails to create the alignment. Territory Planning creates the Root Area territory automatically during that process.

Field-Level Security

Territory Planning follows field-level security for custom area fields. If you give a user access to an alignment that includes custom area fields they don't have access to, Territory Planning notifies them. The fields stay in the alignment. Territory Planning disables those fields and shows the value as null.

Deleted Fields

If a custom area field that you added to an alignment is deleted, Territory Planning informs the user and prompts them to remove the field as an attribute.

Supported Field Types

Most field types are supported. Territory Planning imports these field types:

• Auto Number
• Lookup
• Formula
• Checkbox
• Currency
• Date
• Email
• Geolocation
• Number
• Percent
• Picklist
• Multi-select picklist
• Text

Calculated Attributes

A calculated attribute can include a custom area field. If you remove that field from the alignment, the calculated attribute shows 0 for every area.

Cloned Alignments

When you clone an alignment, Territory Planning includes the custom area fields you added.

• For a formula field, Territory Planning clones the formula definition and recalculates the value when you save.
• Territory Planning doesn't copy Auto Number values when you clone an alignment. Each area gets a value from Salesforce auto-number sequencing.

Legend Search

Legend search doesn't include every field type. Boolean fields aren't included.

Snapshot Restoration

• When you restore a snapshot, Territory Planning includes formula fields. The value for each area comes from the formula output.
• When you restore a snapshot, Territory Planning includes Auto Number fields. The value for each area comes from Salesforce auto-number sequencing.