Considerations for Overriding Standard Buttons | Salesforce
Considerations for Overriding Standard Buttons
Before you override a standard button, review these considerations.
Available in: Salesforce Classic
Available in: Enterprise, Performance, Unlimited, and Developer Editions
Visualforce overrides also available in: Contact Manager, Group, and Professional Editions
Record types available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions
User Permissions Needed
To override standard buttons:
If you override a standard button in Salesforce, that button is still available in Connect Offline or Salesforce Classic Mobile, but it retains its original behavior.
A standard button (New, Edit, View, Delete, and Clone) overridden with a Visualforce page doesn’t show up in Salesforce1 unless the Visualforce page is enabled for Salesforce mobile apps. Overriding standard list and tab controls isn’t supported in Salesforce1.
The View standard button refers to all links in Salesforce that display the detail page for a record. Overriding the View standard button reroutes all these links.
You can have both a Visualforce or s-control override and a Lightning Page override set for the View action at the same time on the same object. In Lightning Experience, the Lightning Page override displays. In Salesforce Classic, the Visualforce or s-control override displays.
If you have the View action overridden with a Visualforce page in Salesforce Classic, the Setup menu on that object record page in Lightning Experience displays the Edit Page option. Selecting Edit Page in Lightning Experience on an object page that’s overridden with a Visualforce page in Salesforce Classic lets you create a custom Lightning Experience record page for that object in the Lightning App Builder.
If a button isn’t available for overrides, you can still hide it on the page layout.
Button overrides affect everywhere that action or behavior is available. For example, overriding the New button on an account also overrides the account option in the Create New drop-down list in the sidebar.
Person Account records use any standard button overrides you make for accounts. Person Account records also use any overrides for the View Self-Service and Enable Self-Service buttons you make for contacts.
If your organization uses the Console tab, overrides for the Edit and View buttons for an object don’t affect the Edit and View buttons in the mini page layouts. Pages that display due to overrides display in the console without the header or sidebar.
To replace a standard button with a custom button, first define the custom button, then customize the page layout to hide the standard button and display the custom one in its place
Because events and tasks don’t have their own tabs, you can only override their standard buttons and links.
You can override buttons on the detail page but not the edit page of a record.
You can only override these standard buttons: New, View, Edit, and Delete.
You can’t add button overrides to an AppExchange package.
You can’t change buttons on lookup dialogs, reports, or tabs. However, you can change the buttons on list view and search result layouts under search layouts.
You can’t relabel or relocate standard buttons on a record detail page.