Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Considerations for Customizing Overrides
Overriding Tabs Using a Standard List Controller
Define Custom Buttons and Links to Visualforce Pages
Adding Custom List Buttons using Standard List Controllers
Displaying Record Types
Remove a Custom Override
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Remove a Custom Override

Learn how to restore the default behavior of a standard button and tab.
  1. From Setup, click Object Manager, and then click the object that you want to update.
  2. Click Buttons, Links, and Actions, and then select Edit from the dropdown of the desired button or tab home page.
  3. To remove the behavior in Salesforce Classic, select No override (default behavior). To remove the behavior in Lightning Experience or the Salesforce mobile app, select Use the Salesforce Classic override.
  4. Save your changes.

    When switching from Salesforce Classic to Lightning Experience, if the URL contains nooverride=1 in Salesforce Classic, it changes to nooverride=true in Lightning Experience, and you don’t see overrides for the record you’re navigating to.

    Note