I have moved my update set to test and committed but i need to do few changes in dev instance

[Srinivasu2]

Hi Community,

I have moved my update set to test and committed but unfortunately i need to do few changes in dev instance

Can i create new update set in dev again and move this new update set to test and  commit this new update set in test instance

once committed both update sets, can we use batch update set concept

Old is a parent update set and add new one is  a child or not?

Could you please confirm can i do like this?

Regards,

Srinivasu Sagiraju

[Vedang1]

Hi @Srinivasu2 

The easiest and best practice would be to create a new update set in DEV and move your changes to TEST.

It is possible that you have more fixes after that so you can keep creating new ones as needed (I Usually suffix them with a number eg. Update Set - 2, Update Set -3).

Once you have positive testing results and UAT completed, you should merge the update sets in TEST (Update Set - Merged) and only move the final copy to Production. I've been using this simple practice for 7 years and it is the easiest to keep track of as well.

I only do a parent - child relationship if I have various different requirements within the primary requirement, especially while being worked upon by different members.

Hope this helps.