How to avoid wiping in progress update sets during clone process

[Daemyian]

Hello,

Quick question cloning form production to Dev. What's the best way to avoid wiping out existing update set that are in progress during cloning instance from production to dev instance? The clone profile states it will wipe out in-progress update sets and flagged a warning when cloning.

Can I just set the update sets in DEV to complete and then process clone. What's the best approach to avoid wiping out update set. 

Thanks,

Daemyian

[Matt102]

Hi,

Just to add that, even if you tick the "Preserve updates" checkbox, you will still recieve the warning about losing in progress update sets - even though you don't. I queried this on Hi i.e. the confirmation need revising. As I recall they said they would put it on their to do list...

That said, we are on Quebec (from Paris) and I've not done a clone on this version yet - I suspect you still recieve the incorrectly worded confirmation though!

R,Matt

[swnewton]

We will complete the update sets and export them. After the clone, we import them to Dev and apply them and then create a new update set for further dev work.

[jing3]

Will this work for the updatesets related to a scoped application? Will it works the same way, or it will not work for a scoped app? 

[Mark Manders]

The 'preserve update set' option only works on global scope, so you will still need to export your scoped application update sets separately (and not only for your own applications, but for all scopes except global).

[Viswa2]

If the custom application/ scoped application in sub-production environment are not yet implemented in production. Then good to follow solution suggested by @swnewton 

Otherwise what was suggested by others checking a checkbox in clone profile is good way to handle.