Opportunity Explorer

Org: customertimes9-dev-ed API v66.0 ID: 00Dg700000082HZ
34
Total Fields
30 standard · 4 custom
10
Sales Stages
8 open · 2 closed
2
Validation Rules
2 active · 0 inactive
4
Page Layouts
Default + 3 team layouts
Sales Pipeline
◉ Field Type Composition
≡ Picklist Fields
⊞ All Fields
LabelAPI NameTypeReq?
⚡ Validation Rules
Require_Line_of_Business Active
Line of Business is required for all opportunities
Error on: Line of Business
Line of Business is required.
Require_Opportunity_Type Active
Opportunity Type is required for all opportunities
Error on: Type
Opportunity Type is required.
☷ Page Layouts
D
Opportunity Layout
Default layout — all profiles
M
Opportunity (Marketing) Layout
Marketing team workflows
S
Opportunity (Sales) Layout
Sales team — primary layout for reps
U
Opportunity (Support) Layout
Support team view
Key Relationships
⇋ Lookup Fields (Parent Objects)
⊕ Child Relationships
New Field Impact Analyzer
🔬
Adding: Sales Region (NorthEast / MidWest / SouthEast / West / Central)
Impact analysis for adding a regional picklist field to track sales territory assignment
📋 Proposed Field Specification
Field LabelSales Region
API NameSales_Region__c
Data TypePicklist
ValuesNorthEast · MidWest · SouthEast · West · Central
RequiredRecommended — via Validation Rule
Default ValueNone (explicit selection)
Help TextGeographic region of the sales team working this opportunity
Field HistoryEnable — track region changes
Naming Convention__c suffix matches existing: DeliveryInstallationStatus__c, TrackingNumber__c

Page Layouts — 4 layouts to update

The new field must be added to relevant layouts. Recommended placement:

  • Opportunity (Sales) Layout — Add to "Opportunity Information" section, near Type field. ★ Priority
  • Opportunity Layout — Add to main section for visibility across all teams
  • Opportunity (Marketing) Layout — Add for campaign-to-region reporting
  • Opportunity (Support) Layout — Optional, add as read-only

Validation Rules — New rule needed

Following the org's pattern (see Require_Line_of_Business and Require_Opportunity_Type), create:

  • Rule name: Require_Sales_Region
  • Formula: ISPICKVAL(Sales_Region__c, '')
  • Error: "Sales Region is required."
  • Error field: Sales_Region__c

Reports & Dashboards

New reporting capabilities enabled:

  • Pipeline by Region report
  • Win rate by Region analysis
  • Revenue by Region dashboard component
  • Forecast breakdown by territory
  • Stage velocity comparison across regions

Salesforce Maps Integration

This org has Salesforce Maps installed. The Sales Region field can be:

  • Used as a filter in route planning
  • Linked to Maps territory definitions
  • Auto-populated via Maps geo-assignment rules
  • Visualized on map layers by region color

Security & Visibility

Field-level security configuration:

  • Sales profiles — Read/Write access
  • Marketing profiles — Read-only access
  • Support profiles — Read-only access
  • System Admin — Full access (auto)
  • Consider: Should reps see only their region's opps?

Related Considerations

Check existing fields for overlap:

  • OwnerId — already tracks rep, but not territory
  • LeadSource — lead origin, not geography
  • Account.BillingState — customer location ≠ sales region
  • No existing region field — safe to add
✅ Deployment Checklist
  • Create picklist field Sales_Region__c with 5 values
  • Enable field history tracking
  • Set field-level security for all profiles
  • Add to Opportunity (Sales) Layout — "Opportunity Information" section
  • Add to Opportunity Layout (default)
  • Add to Marketing & Support layouts (read-only)
  • Create validation rule Require_Sales_Region
  • Add to relevant list views (My Open Opportunities, etc.)
  • Update report types to include new field
  • Create "Pipeline by Region" report + dashboard component
  • Backfill existing records with correct region values
  • Evaluate Maps territory auto-assignment integration
  • Test in sandbox before deploying to production
Generated from Salesforce org metadata · customertimes9-dev-ed · sfmaps.mxsh@feb02.2026 · March 2026