Save & New
Save & New in Salesforce is a standard button on record-creation forms that saves the current record and immediately opens a new blank record of the same type, streamlining bulk data entry.
Definition
Save & New in Salesforce is a standard button on record-creation forms that saves the current record and immediately opens a new blank record of the same type, streamlining bulk data entry. The button is the bulk-entry counterpart to the standard Save button (which saves and returns to the record detail page) and the Cancel button (which discards the in-progress entry). For users entering many records of the same type back-to-back (a sales rep logging multiple calls, an admin creating multiple users, a support agent creating sibling Cases), Save & New eliminates the navigation overhead between each record.
The button appears by default on standard object create pages in Lightning Experience and Salesforce Classic. It also appears on custom object create pages unless an admin removes it. Save & New can be hidden through Page Layout configuration, removed for specific record types or profiles, or replaced with a custom Quick Action that implements equivalent behavior. The default behavior is consistent across the platform: save the current input, redirect to a fresh creation form for the same object, optionally pre-populating fields based on the prior entry.
How Save & New streamlines bulk data entry on the Salesforce platform
What Save & New does and why it exists
Save & New optimizes the data entry workflow for users who create many records of the same type in one session. Without the button, a user creating 20 Cases for a single customer would: click New on the Case object, fill the form, click Save, get redirected to the Case detail page, click back to the Account, click New on Cases again, fill the form, click Save, and so on. Each cycle includes three to five navigation clicks. Save & New collapses this to: click New, fill the form, click Save & New, fill the next form, click Save & New, repeat. The reduction in navigation friction is substantial; bulk-entry sessions become smooth instead of tedious. The button is the difference between admins who can quickly create 50 users in a session and admins who give up after the tenth.
Where Save & New appears and when it does not
Save & New appears by default on the standard New record creation pages for most objects in both Lightning Experience and Salesforce Classic. It does not appear when the user creates a record from a different starting context (a New Contact from the Account record Contacts related list returns to the Account, not to a new Contact form). Custom Page Layouts can hide the button. Some objects do not have Save & New for product reasons (Cases sometimes hide it because the workflow assumes a single Case per session). Custom Lightning record pages built in Lightning App Builder may or may not include Save & New depending on the Lightning Component used; the standard Record Form component includes it, but custom components may not.
Field pre-population and the sticky-field pattern
Save & New supports field pre-population through URL parameters and through the platform sticky-field behavior. When the user clicks Save & New, the platform optionally carries forward field values from the previous record into the new blank form. Fields configured as Sticky in Salesforce Classic (a per-user setting) and the equivalent Lightning Experience behavior pre-populate based on the prior entry. URL hacks (links that pre-populate fields through query string parameters like /lightning/o/Contact/new with defaultFieldValues=AccountId=001xxx) let admins build custom Save & New experiences that retain context across creations. Mature data entry workflows use these techniques to reduce per-record typing further; the user only fills the fields that genuinely change between records.
Save & New permissions and the record creation context
Save & New respects every Salesforce permission layer. The user must have Create permission on the object to see the New button (which then includes Save & New). Field-level security determines which fields appear on the creation form and which can be edited. Record types may restrict which combinations of values the user can choose. Validation rules fire on Save & New the same way they fire on regular Save; a validation rule that blocks the current record blocks the Save & New attempt and keeps the user on the form to fix the issue. Cross-object permissions matter too: a user creating a Case under an Account needs Read access to the Account; without it, the lookup field fails.
Custom Save & New: Quick Actions and Apex behavior
Admins who need behavior beyond the standard Save & New can build a Quick Action that implements custom logic. A common pattern is a Quick Action with type Create that pre-populates specific fields based on the user role or the source record. Apex can also implement Save & New behavior in custom Visualforce or Lightning components by chaining a save operation followed by a redirect to a fresh edit page. For Cases or other Service Cloud objects, custom Save & New buttons often integrate with the Service Console open-tab pattern, opening the new record in a separate Console tab rather than redirecting away from the current context. Plan the custom behavior carefully; users have strong expectations from the standard Save & New, and deviating produces frustration.
Hiding or removing Save & New
Some workflows want to remove Save & New to enforce a different post-save behavior. Common reasons: the workflow assumes the user reviews the created record before creating another, the next step is on a different object, or the data entry pattern is genuinely one-at-a-time. Hide Save & New through Page Layout configuration (remove the button from the Standard Buttons section of the page layout). For Lightning record pages, the button removal happens through the Lightning App Builder configuration of the relevant component. Document the decision in the page layout runbook so future admins understand why the button is missing; without documentation, a future admin may add it back without realizing it was deliberately removed.
Configuring Save & New for productive bulk entry
Configuring Save & New is a small but high-impact UX decision. The four-step routine covers: review whether Save & New is appropriate for each object, customize the page layout to include or exclude it, configure field pre-population to reduce per-record typing, and (if needed) build a custom Quick Action for non-standard behavior. Each step is a different lever; together they shape how efficient bulk data entry is for users who actually do it.
- Review whether Save & New is appropriate per object
For each object, identify whether users actually enter records in bulk. Objects with high-volume single-session entry (Tasks, Activities, certain custom objects) benefit from Save & New. Objects with low-volume careful entry (Opportunities, customer-facing Cases) may not. Document the per-object decision: keep, remove, or customize Save & New. Get input from the user community; users who do the entry know what they need. Without their input, the decision is admin-side guesswork that may not match the actual workflow.
- Customize the page layout
For each object where Save & New should appear, confirm it is on the page layout assigned to the relevant profile or record type. For objects where it should not appear, remove it from the Standard Buttons section of the page layout. Save the layout and test with a target user. For Lightning record pages built in Lightning App Builder, the Record Form component includes Save & New by default; custom components may need configuration. Document the per-layout decision in the page layout runbook.
- Configure field pre-population for sticky values
For fields that should carry forward from the previous record (the same Account on the next Contact, the same Status on the next Case), configure them as Sticky in the user personal settings, or use URL parameters in the New button to pre-populate. For high-volume workflows, build a custom Save & New via Quick Action that pre-populates fields based on the source record. Test the pre-population with realistic data; some pre-populations make sense (Account) and others do not (record-specific names). Iterate based on user feedback.
- Build a custom Quick Action for non-standard behavior
If the workflow needs behavior beyond what the standard Save & New offers (open in a Service Console sub-tab, pre-populate from the parent record, run additional Apex on save), build a Quick Action. From Setup, Object Manager, the object, Buttons Links and Actions, New Action: pick the Create type, configure the field layout, add any pre-populated values. Place the custom action on the page layout in place of (or alongside) the standard Save & New. Document the custom action so future admins understand why the standard button was replaced.
- Save & New does not appear when the user creates the record from a related list. The user lands back on the parent record, not on a new blank form. Use a custom Quick Action if bulk creation from a related list is the workflow.
- Save & New respects validation rules. A failing validation blocks the save and keeps the user on the form, which is the same behavior as regular Save.
- Custom Lightning components may not include Save & New automatically. The standard Record Form component does; custom components need explicit configuration or rebuilt buttons.
- Sticky fields differ between Classic and Lightning. The Classic per-user sticky setting does not directly translate; Lightning uses platform-level pre-population behavior. Test in both UIs if both are used.
- Removing Save & New affects user productivity. Before hiding it, confirm with the actual users who do the entry; admins removing it for aesthetic reasons often surprise the team with productivity loss.
Trust & references
Straight from the source - Salesforce's reference material on Save & New.
- Customize Page LayoutsSalesforce Help
- Create Quick ActionsSalesforce Help
- Navigate Lightning ExperienceSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Save & New do?
Q2. When is it useful?
Q3. Where is the button?
Discussion
Loading discussion…