function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
DML2020DML2020 

Validation and deploy best practice

If a changeset is successful in validation and deployment from a developer sandbox to a full sandbox, then successfully tested, should the changeset then be validated and deployed from the full sandbox to production or can the changeset be validated and deployed from the developer sandbox directly to the production environment.

Does the path matter as long as it has been tested in the full sandbox first before sending over to production?

Best Answer chosen by DML2020
Vishwajeet kumarVishwajeet kumar
Hello,
As per Standard Software development practices deployment should be done from an org which is something like Integration/UAT testing org or even something more closer to Production, before going to Production. It stops unwanted/unintended deployment troubles.

In your case full sandbox might be good idea.

Thanks

All Answers

Vishwajeet kumarVishwajeet kumar
Hello,
As per Standard Software development practices deployment should be done from an org which is something like Integration/UAT testing org or even something more closer to Production, before going to Production. It stops unwanted/unintended deployment troubles.

In your case full sandbox might be good idea.

Thanks
This was selected as the best answer
SwethaSwetha (Salesforce Developers) 
Acknowledging the above comment, in Full sandbox, all data is copied over from the production instance implying it is very similar to production org and the scope of errors would be less. The path does not seem to matter in your case considering your statement that everything is thoroughly tested and validated. However, recommended approach to deploy via full copy.

Please mark the answer as best if it helps.Thank you