Considerations for Customizing Overrides

Get familiar with these considerations before you override the behavior of a standard button or tab.

General Considerations

When overriding buttons with a Visualforce page, use the standard controller for the object on which the button appears. For example, to use a page to override the Edit button on accounts, the page markup must include the standardController="Account" attribute on the <apex:page> tag.
1<apex:page standardController="Account">
2<!-- page content here -->
3</apex:page>

When overriding tabs with a Visualforce page, you can select only Visualforce pages that use the standard list controller for that tab’s associated object, pages with a custom controller, or pages with no controller.

Use a controller extension to add extra functionality to Visualforce page that you’re using as an override.

Tip

When overriding lists with a Visualforce page, you can select only Visualforce pages that use a standard list controller.

When overriding the New button with a Visualforce page, you can choose to skip the record type selection page. If you do, new records you create aren’t forwarded to the record type selection page. Salesforce assumes that your Visualforce page is already handling record types.

When a Salesforce mobile app user clicks New to create a product, the user must select a record type even if the Skip record type selection page option is selected in Setup.

Important

Specific Override Considerations

When the ResetPassword action for an Experience site is set to a Visualforce page, the page’s action that triggers the password change must redirect to a different page to avoid an infinite password reset loop.