1 Reply · Latest reply on Dec 7, 2017 8:04 PM by Gowtham S

    Best practice for moving update sets

      Hi gang,

      here's a best practice question for update sets.

       

      I've seen several posts stating that best practice is to move update sets from DEV to TEST, and then from TEST to PROD.

       

      My question is why is that specifically? 

       

      For several logical reasons, I think a case could be made for migrating from DEV to TEST, and then from DEV to PROD.

       

      thoughts?

        • Re: Best practice for moving update sets
          Gowtham S

          You move an update set from Dev to TEST, and while performing your validations on TEST, you found out that you have accidentally added an additional field / a BR / script include (while testing in dev), which is actually not required. You delete that update from your update set in TEST.

           

           

          When you move to PROD, from DEV,you will still have these issues, which will cause a redundant work.