Understanding Column Configuration
Dispatch Board columns determine what information dispatchers see for each job, enabling quick assessment and efficient scheduling decisions.
Column Planning
Before configuration, identify essential information:
Critical Job Information
- Job number/identifier
- Date and time
- Service type/category
- Current status
- Customer name
- Location details
Optional Information
- Priority level
- Assigned engineer
- Duration estimate
- Special instructions
- Contract coverage
Configuring Dispatch Board Columns
Step 1: Access Custom Metadata Types
Navigate to the configuration area:
- Go to Setup (gear icon)
- In Quick Find, search for “Custom Metadata Types”
- Click Custom Metadata Types
- Locate and click Settings
Step 2: Access DB Settings
Find the dispatch board configuration:
- In the Settings metadata type
- Click Manage Records
- Look for DB Settings
- Click Edit on the DB Settings record
Step 3: Understanding the JSON Structure
The column configuration uses JSON format:
json
[
{
“Field”: “Display Label”,
“Value”: “API_Field_Name”
}
]
Structure Explanation:
- Field: What users see as column header
- Value: Actual Salesforce field API name
- Array format allows multiple columns
- Order matters for display sequence
Step 4: Configure Standard Columns
Enter the standard column configuration:
DB Table Columns field:
json
[
{
“Field”: “JOB NO”,
“Value”: “Name”
},
{
“Field”: “DATE AND TIME”,
“Value”: “fax__Planned_Visit_Date_Time__c”
},
{
“Field”: “CATEGORY”,
“Value”: “fax__Visit_Type__c”
},
{
“Field”: “STATUS”,
“Value”: “fax__Status__c”
}
]
This configuration displays:
- JOB NO: The job number/identifier
- DATE AND TIME: Scheduled visit time
- CATEGORY: Type of service
- STATUS: Current job status
Step 5: Adding Additional Columns
To add more columns, extend the JSON:
json
[
{
“Field”: “JOB NO”,
“Value”: “Name”
},
{
“Field”: “DATE AND TIME”,
“Value”: “fax__Planned_Visit_Date_Time__c”
},
{
“Field”: “CATEGORY”,
“Value”: “fax__Visit_Type__c”
},
{
“Field”: “STATUS”,
“Value”: “fax__Status__c”
},
{
“Field”: “CUSTOMER”,
“Value”: “fax__Customer__r.Name”
},
{
“Field”: “PRIORITY”,
“Value”: “fax__Priority__c”
},
{
“Field”: “DURATION”,
“Value”: “fax__Estimated_Duration__c”
}
]
Step 6: Save Configuration
After entering the JSON:
- Click Save
- Configuration takes effect immediately
Advanced Column Configuration
Related Object Fields
Display data from related records:
json
{
“Field”: “CUSTOMER CITY”,
“Value”: “fax__Customer__r.ShippingCity”
}
Relationship Syntax:
- Use __r for relationships
- Add .FieldName for specific field
- Supports multiple levels
Formula Fields
Include calculated values:
json
{
“Field”: “TIME UNTIL DUE”,
“Value”: “fax__Hours_Until_Due__c”
}
Custom Fields
Add organization-specific fields:
json
{
“Field”: “REGION”,
“Value”: “Region__c”
}
Column Best Practices
Essential Columns
Always include:
- Job identifier
- Date/time
- Status
- Customer reference
- Service type
Performance Considerations
- Limit to 7-10 columns
- Avoid complex formulas
- Minimize related object queries
- Use indexed fields when possible
User Experience
- Order by importance
- Use clear labels
- Consistent naming
- Appropriate column width
