Print this page

Salesforce1 - Behavior When Overriding View, New, and Edit Actions

Knowledge Article Number 000212844
The Salesforce1 mobile application behaves differently than the Salesforce Classic UI and Lightning Experience UI when using overrides on object actions such as View, Edit, and New. 


With any navigation in Salesforce1 developers should be utilizing our "" navigation object that is provided by default with Visualforce pages in Salesforce1. The Page Reference class that is generally used in the Classic Salesforce interface is not supported in Salesforce1 and should be avoided. Please review the following article discussing navigation methods for Salesforce1:
Salesforce1 - Visualforce Navigation Methods and Page Reference Support

Difference from the Classic Salesforce and Lightning Experience Interface

When you override the View, New, or Edit actions of an object some developers are familiar with bypassing the override to access the standard Page Layout by including the "nooverride" parameter in the URL. This parameter is not officially supported for the Classic or Lightning Experience interfaces.

In Salesforce1 the nooverride parameter is supported for use ONLY with the View action in combination with using the navigation function.

The nooverride parameter is not supported in Salesforce1 for the New or Edit actions. If you override the New or Edit actions you may not be able to navigate back to the standard page for that action in Salesforce1. If your override page tries to navigate to the same New or Edit action and bypass the override, the app may display a blank or cycling screen as the page used as an override tries to load itself in a loop. 
  • To bypass the override on the View action for an object use the navigateToURL function. For example:'/recordId?nooverride=1').
  • The alternative approach,[, view]), will always load the override and cannot accept the nooverride paramter.
  • The nooverride parameter is not supported for creating records with the navigateToURL function. For example:'/objectPrefix/e?nooverride=1') may not behave as expected.
  • The alternative approach,[, recordTypeId]), will always load the standard page ignoring the override.
  • When a New override is set and it is not defined to "Skip Record Type Selection Page" via the checkbox for the Override Properties, then users will be presented with the Classic UI page for selecting a Record Type before being navigated to the defined Visualforce page.
  • The nooverride parameter is not supported for editing records with the navigateToURL function. For example:'/recordId/e?nooverride=1') may not behave as expected. 
  • The alternative approach,, will always load the override and cannot accept the nooverride parameter.

promote demote