Newer Version Available
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.
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.