Account Object & Account Team

Account Object & Account Team Integration

Alternative approach for organizations not using Enterprise Territory Management.

How It Works

BoogieBoard writes territory information directly to custom fields on the Salesforce Account object and manages territory assignments through Account Team memberships.

Custom Fields Added to Account Object

BoogieBoard automatically creates and manages the following custom fields on the Salesforce Account object:

Screenshot 2025-07-28 at 15.52.20.png

Field Name	API Name	Purpose
Territory Name	BoogieBoard_Territory__c	Primary territory assignment (e.g., "East")
Territory ID	BoogieBoard_Territory_ID__c	BoogieBoard territory identifier (e.g., "5657")
Scenario Name	BoogieBoard_Scenario__c	Planning scenario name (e.g., "FY27 Sales Global")
Scenario ID	BoogieBoard_Scenario_ID__c	BoogieBoard scenario identifier (e.g., "288")
BB Level 1	BoogieBoard_Level_1__c	Top hierarchy level (e.g., "All Accounts")
BB Level 2	BoogieBoard_Level_2__c	Second hierarchy level (e.g., "NAMER")
BB Level 3	BoogieBoard_Level_3__c	Third hierarchy level (e.g., "NAMER STRAT")
BB Level 4	BoogieBoard_Level_4__c	Fourth hierarchy level (e.g., "East")
BB Level 5	BoogieBoard_Level_5__c	Fifth hierarchy level (e.g., "Territory 4")
Territory Path	BoogieBoard_Territory_Path__c	Full hierarchical path
Last Sync Date	BoogieBoard_Last_Sync__c	When territory assignment was last updated

Field Population Logic

Salesforce Account: Acme Corporation
│
├── Territory Assignment Details
│   ├── BoogieBoard_Territory__c: "East"
│   ├── BoogieBoard_Territory_ID__c: "5657"
│   └── BoogieBoard_Last_Sync__c: "2025-07-28 14:30:15"
│
├── Planning Context
│   ├── BoogieBoard_Scenario__c: "FY27 Sales Global"
│   └── BoogieBoard_Scenario_ID__c: "288"
│
├── Territory Hierarchy Structure
│   ├── BoogieBoard_Level_1__c: "All Accounts"      ← Root Level
│   │   └── BoogieBoard_Level_2__c: "NAMER"          ← Regional
│   │       └── BoogieBoard_Level_3__c: "NAMER STRAT" ← Strategic
│   │           └── BoogieBoard_Level_4__c: "East"    ← Area
│   │               └── BoogieBoard_Level_5__c: "Territory 4" ← Individual Territory
│   │
│   └── BoogieBoard_Territory_Path__c: "All Accounts > NAMER > NAMER STRAT > East > Territory 4"
│
└── Resulting Territory Structure:
    All Accounts
    └── NAMER (North America)
        └── NAMER STRAT (Strategic Accounts)
            └── East (Eastern Region)
                └── Territory 4 (Final Assignment)

The hierarchy fields are populated based on the BoogieBoard territory structure:

Level 1: Always the root node (typically "All Accounts" or similar)
Level 2: Regional grouping (e.g., "NAMER", "EMEA", "APAC")
Level 3: Sub-regional or strategic classification (e.g., "NAMER STRAT")
Level 4: Territory group or area (e.g., "East", "West")
Level 5: Individual territory assignment (e.g., "Territory 4")