Starting with FSL managed package v262 (Summer '26), the legacy Field Service tab was renamed to Classic Dispatch Console as part of the Scheduling Console general availability launch.
Any custom configuration that references the old Field Service tab label — including Visualforce page references, custom tabs, page layouts, or navigation rules — breaks after the upgrade because the tab no longer exists under that name.
This article covers:
This article does not cover:
The tab rename is intentional. FSL v262 reorganized the dispatcher experience to distinguish the legacy Classic Dispatch Console from the new Scheduling Console tab. Managed package tabs cannot be directly renamed — they are controlled by the package.
vf001_ServiceExpert is installed by the managed package. If it does not appear in your org, reinstall or update the Field Service managed package.)Step 1 — Create a custom Visualforce tab
vf001_ServiceExpert.Field Service).Step 2 — Add the custom tab to the Field Service app
Users will now see your custom tab label in the Field Service app navigation.
Custom tab does not appear in app navigation Verify you added the tab to the Field Service app in App Manager and saved. Refresh your browser and clear the cache.
Both the custom tab and managed package tab appear Expected behavior. Remove the managed package tab from the app's tab list in App Manager if you want only your custom tab to show.
Custom tab shows a blank page or error Verify vf001_ServiceExpert exists under Setup → Custom Code → Visualforce Pages. If missing, reinstall or update the FSL managed package. If the page exists but still errors, confirm your org's Trusted URLs include the Salesforce Lightning domain (Setup → Session Settings → Trusted URLs).
This custom tab is a workaround for a managed package constraint. If Salesforce makes further changes to the Dispatcher Console tab structure in future releases, you may need to update the custom tab configuration. Creating a custom tab does not automatically migrate existing Visualforce page configurations — update any page layouts, navigation rules, or custom code that still reference the old tab name manually.
005389875

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.