Find your content:

Search form

You are here

Change Sets and Sandbox Refresh


If I were to create and upload an outbound Change Set from a Salesforce Sandbox to Production, then (without Deploying the Change Set in Production) refresh the Sandbox, would I still be able to Deploy the Change Set in Production after the refresh is complete (even if the object no longer exists due to the refresh)?

Attribution to: Matt K

Possible Suggestion/Solution #1

That should be able to work without a problem, as the changeset you upload is a snapshot of the moment you press upload, then all the metadata you upload is flattened to (I guess) an xml file, and put available on a production environment. You could test that without having to refresh your sandbox, by simply uploading some code, change the code on your sandbox before doing the deploy on your production, and see the result.

Attribution to: pjcarly

Possible Suggestion/Solution #2

I just had this same scenario. We had change sets to deploy to our production instance after our sandbox refresh, and due to business reasons, we were unable to change when we did our refresh vs release.

Although deleting an outbound change set from the source organization will also delete it from the target organization, this does not appear to be the case between sandbox and production when the sandbox is refreshed.

I have no idea why this is the case, and there is no documentation I can find about it.

Attribution to: Julie
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content