Loading

Custom Visualforce Pages Not Loading After Classic Dispatch Console Tab Rename in FSL v262

Publiseringsdato: Jul 24, 2026
Beskrivelse

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:

  • Why the tab rename breaks custom Visualforce navigation
  • How to restore access using a custom Visualforce tab

This article does not cover:

  • Renaming standard (non-managed-package) tabs, which can be customized directly via App Builder
  • Dispatcher Console loading errors unrelated to the tab rename (permission issues, VF domain trust errors)
Løsning

Cause

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.

Prerequisites

  • FSL managed package v262 or later is installed in your org. (The Visualforce page vf001_ServiceExpert is installed by the managed package. If it does not appear in your org, reinstall or update the Field Service managed package.)
  • You have System Administrator access, or a profile with the Customize Application permission, to create Visualforce tabs and edit apps in App Manager.

Resolution

Step 1 — Create a custom Visualforce tab

  1. In Setup, search Tabs in Quick Find and open Tabs.
  2. Under Visualforce Tabs, click New.
  3. In the Visualforce Page drop-down, select vf001_ServiceExpert.
  4. In the Tab Label field, enter the label your configurations expect (for example, Field Service).
  5. Choose a tab icon and click Save.

Step 2 — Add the custom tab to the Field Service app

  1. In Setup, search App Manager in Quick Find and open App Manager.
  2. Find the Field Service app and click Edit.
  3. In the tab list, add your newly created custom Visualforce tab.
  4. Reorder tabs if needed. To remove the managed package tab, delete it from the tab list.
  5. Click Save.

Users will now see your custom tab label in the Field Service app navigation.

Verification

  1. Open the Field Service app in Lightning Experience.
  2. Confirm your custom tab appears in the navigation bar with the label you specified.
  3. Click the tab to confirm it loads the Classic Dispatch Console and displays expected functionality.
  4. If you removed the managed package tab, confirm it no longer appears.

Troubleshooting

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).

Note

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.

Knowledge-artikkelnummer

005389875

 
Laster
Salesforce Help | Article