Starting with Salesforce Field Service package version 262 (Summer '26 release), the Dispatcher Console tab underwent a naming change as part of the Scheduling Console general availability launch. The legacy 'Field Service' tab is now labeled 'Classic Dispatch Console.' If your custom Visualforce pages, page layouts, or navigation configurations reference the old tab name, those references break after the upgrade.
The Dispatcher Console tab rename is an intentional product change. Salesforce Field Service v262 introduced the new Scheduling Console as a general availability feature and reorganized the dispatcher experience. As part of this reorganization, the legacy 'Field Service' tab (which hosted the Classic Dispatch Console) was renamed to 'Classic Dispatch Console' to distinguish it from the new Scheduling Console tab.
Any custom configuration—including Visualforce page references, custom tabs, page layouts, or navigation rules—that hardcodes or references the old 'Field Service' tab label will break because the tab no longer exists under that name.
To restore navigation to your custom Visualforce pages after the tab rename, create a custom Visualforce tab that references the legacy tab name:
1. From Setup, navigate to Integrations > Visualforce Pages.
2. Locate and open the Visualforce page you want to display (e.g., `vf001_ServiceExpert` or your custom page).
3. From Setup, navigate to User Interface > Tabs > Visualforce Tabs.
4. Click **New**.
5. Select your Visualforce page from the **Visualforce Page** drop-down.
6. In the **Tab Label** field, enter `Field Service` (or the label your custom configurations expect).
7. Choose a tab icon and click **Save**.
8. Navigate to the Field Service app in App Manager.
9. Add the newly created custom tab to the Field Service app, either replacing the 'Classic Dispatch Console' tab or alongside it.
10. Save the app configuration.
Your custom Visualforce pages will now load when users navigate to the 'Field Service' tab in the Dispatcher Console.
- The custom 'Field Service' tab is a workaround and does not prevent future product changes. If Salesforce makes additional changes to the Dispatcher Console in future releases, you may need to update your custom tab configuration again.
- Creating a custom tab does not automatically migrate existing Visualforce page configurations from the old 'Field Service' tab. You must manually update any page layouts, navigation rules, or custom code that reference the old tab name.
- If you have multiple Visualforce pages that were previously accessible via the 'Field Service' tab, you may need to create multiple custom tabs (one per page) or use a custom navigation menu to consolidate access.
Starting with Salesforce Field Service package version 262 (Summer '26 release), the Dispatcher Console tab underwent a naming change as part of the Scheduling Console general availability launch. The legacy 'Field Service' tab is now labeled 'Classic Dispatch Console.' If your custom Visualforce pages, page layouts, or navigation configurations reference the old tab name, those references break after the upgrade.
005388196

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.