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

[Madhan27]

Hi @Community Alums , I have moved multiple update sets from DEV to test with version V2,V3 &V4 for sprint 5, But I didnt tag any parent update set to the updatesets as I have closed the parent update set in the Dev instance, Can I tag the V2,V3 &V4 to parent update set which i am having for Sprint 5 in the test instance and make it as a batch?

[Sumanth16]

Hi @Madhan27 ,

Yes,if you have admin access you can do it. You can merge update sets and promote another non-prod instance before promoting to prod and test it.

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[Vijay Balotia1]

Hi Srinivasu,

Yes its always a good practice to capture your new changes in Dev, and then move it to higher instance.

There are two options:

1. Batch update set on higher instance if possible

2. Create versioning of your update set simply keep conversion with version detail and move update in sequence 

Thanks,

Vijay Balotia

Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.
Thanks
Vijay Balotia

[Vedang1]

I would not advise to open an Update set that you have already closed in DEV (unless immediately). If you have multiple developers and they may be working on the same configuration, it can be impacted.

The safest way is to create a new update set with suffix "... - 2" so you know its the 2nd one, and move to TEST once ready. You can keep doing this with 3, 4 etc. if you have more changes required after UAT.

Once the final UAT is completed and you are ready to move to Prod, instead of using batch, what I do is merge all the related update sets into one with suffix "... - FINAL". This is the one that I move to Production.

[asifnoor]

Hi,

Yes, you can create a new update set in dev and commit to your test intance. Then simply you can merge these update sets in INT before deploying to prod, that is more easier solution.

Mark the comment as a correct answer and helpful if this has helped to solve your problem.