Get your FREE 30-day trial.
Please complete all fields.
The Salesforce Summer ‘18 release is quickly approaching and soon you'll be able to take advantage of exciting new features and functionality! If you are a Sandbox customer, you have the opportunity to get early access to Summer ‘18 in your Sandbox and test new customizations and features before your production organization is upgraded.
Note: The blog includes special considerations for Sandbox Cloning Beta participants.
The Sandbox Preview window for Summer ‘18 is scheduled to begin May 4, 2018. If you would like your Sandbox organization to take part in the Summer ‘18 Preview, your Sandbox must be active on a Preview Instance before May 4, 2018 to take part in an overall instance upgrade.
Please read carefully and follow the instructions in the next section for specific information on how to handle each of your Sandboxes. In most cases, you will not need to do anything because your Sandbox is already on a preview instance. But you may need to take action before May 4, 2018 in order for your Sandbox to take part in the Summer ‘18 Preview.
General Information about the Sandbox Service:
Sandbox Instances are split up in two groups – Preview and Non-Preview. Preview Instances are instances which get upgraded to the newer version of Salesforce before Production Instances (e.g. NA2, EU1, AP0) and Non-Preview Instances are upgraded towards the end of a Major Release along with the majority of Production Instances. For the Summer ’18 Release, the Preview Instances will be upgraded to Summer ’18 on May 4 and May 5, 2018 and Non-Preview Instances will be upgraded to Summer ’18 on June 8 and June 9, 2018.
Between now and May 4, 2018 all sandbox requests will be routed to Preview Instances. Sandboxes that complete in time for the major release on May 4, 2018 will be upgraded to the newer version of Salesforce.
On May 4, 2018, all incomplete sandbox requests will be reset on a Non-Preview Instance and pending and new sandbox requests will be routed to Non-Preview Instances until your Production Instance is upgraded to Summer ‘18.
You have from now until May 4, 2018 to decide if you would like your Sandbox to take part in the Summer ‘18 Preview. Follow the steps below for each Sandbox org that you have.
Note: If you have a full Sandbox, be mindful of the 29-day refresh policy and plan accordingly.
I need to create a new Sandbox – What are my options?
I have an existing Sandbox – What are my options?
1) Determine your Sandbox instance
To determine which instance your Sandbox is on, log into your production org and navigate to your Sandbox List page (Search “Sandbox” in the Quick Find bar on the Setup Home Page).
Determine your Sandbox instance by using the Location column above.
2) Refresh? Or Don’t Refresh? Or Do Nothing?
Once you have located the instance that your Sandbox is on, use the chart below to determine if, when, and what action you should take on your Sandbox.
Notes:
AppExchange Preview Instructions
If you plan to upload and/or install one or more AppExchange packages using your Sandboxes during the Sandbox Preview Window, you should use the chart below to determine your course of action.
If you have additional questions about your Sandbox options in conjunction with the Summer ‘18 release, please contact Salesforce Customer Support.
IMPORTANT - Plan Ahead!
Due to the popularity of the Sandbox Preview program, there are often backlogs in Sandbox create and refresh requests. Since all incomplete sandboxes will be reset to a Non-Preview Instance prior to the deadline on May 4, 2018, it is a recommended practice to request your sandbox a week in advance of the deadline to improve your chances of obtaining a completed Sandbox on a Preview Instance. While we strive to process each request in a timely manner, we cannot guarantee completion of the Sandbox before the deadline.
Sandbox Cloning Beta
You can only clone Sandboxes that are on the same major Salesforce version as the production org. Sandboxes that are upgraded as part of the preview on May 4, 2018 will not be available for cloning until the production org is upgraded to the new release.
Additional Information
