Review End2End Sandbox Management Tutorial here
Salesforce end2end deployment video - sfdconestop playlist
Sandbox Refresh Preview/non Preview Recommendations
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.
Review detailed video here -
Note - For every release, Salesforce announces preview cutoff date and during this preview window, all sandbox refresh will auto redirected to preview instance, need to work with support to route to non preview. Post cutoff date, preview instances get auto upgraded to the latest release and any refresh initiated post preview cutoff date will have the same release of production org with no exception. Check out the above video for more details!!
You can key in your instance name like cs87 at the instance of the below url to understand what action to be take to stay in preview/non preview mode-
Sample format -
https://sandbox-preview.herokuapp.com/sandbox/cs87
For multi sandbox instances -
https://sandbox-preview.herokuapp.com/sandbox/cs87,cs88,cs89,cs90
Q: Is it possible to move my sandbox that received the release preview off the preview without a refresh?
A: No, in order to move a sandbox off of the release preview you will need to submit a refresh to direct the copy to a non-preview instance.
There are no exceptions and a refresh is always required in this circumstance because the preview upgrade is applied to the entire instance and not at the org level which is why a refresh is required to move the sandbox currently located on a preview instance to non-preview instance.
Q: Is it possible to upgrade my sandbox to the preview after the preview release date has passed?
A: No, since your production environment is still on the current release it is not possible to move an existing or refresh a new sandbox copy onto the release preview. The release version of a sandbox will always match the version of its production organization at the time of the copy.
This is why the sandbox preview window is important because it is designed to allow you to direct copies to sandbox instances that will be receiving an early upgrade or preview of the next release. The preview instances are all upgraded on a specific date. The only way to have sandbox on the release preview is for the refresh to be completed with the sandbox located on a preview instance so it can be upgraded with the instance.
If the preview upgrade date has passed it is no longer possible to direct copies or move a sandbox onto the release preview. The next opportunity to refresh a sandbox to the next major release will be after your production instance has been upgraded or you can clone a sandbox which is on the latest release.
Should you need to test in a preview org, the only recommendation is to sign up for a pre-release org. The sign up link is typically posted in the Salesforce Blog entry for each major release.
Recommendations to reduce sandbox refresh processing time -
Exclude Field Tracking History data and Chatter Data, use templates to exclude the objects of high storage for example exception logger objects to reduce the sandbox refresh processing time
https://help.salesforce.com/s/articleView?id=sf.data_sandbox_refresh.htm&type=5
Data Mask - https://help.salesforce.com/s/articleView?id=sf.data_mask_overview.htm&type=5
No comments:
Post a Comment