Saving off 'in progress' update sets for a clone

[ljschwaberow]

Our DEV instance is in great need of a clone but I have multiple update sets that are 'in progress' and I have more work to do on all of them. I have read up on Saving Customizations in a single XML file on the Wiki. However, I have to set this the update sets to complete to do this. Can I just export the update sets, clone the instance, import the update sets and then create new update sets from there? Shouldn't it capture everything that I've currently done plus the new changes? More specifically each of these update sets is a new Change Request form. I am still new to export/importing update sets and I don't want to lose all the work I've done.  

[jfreise]

Hi Lindsey,

If you want to export them while they are still "In Progress" you will have to edit the UI Action for the Export to XML link. Remove the condition that shows the link when state is "Complete". Now you can export an update set at any state. After the clone, you can go to the bottom of Retrieved Update Sets and use the Import Update Set from XML link to being in each one. After previewing and committing each one, you will notice them back in your local update sets, but are all "complete". Just set them back to "In Progress" and you are back where you were before the clone.

Good luck,

Jay

[Community Alums]

Hi,

Can we export the update sets those are 'In progress' and can we import into instance. will it causes any issues.

what are action have to take while doing that. If we are not able to import in progress update sets to instance, what any workaround to do on exported XML file.

Thanks,

Swamy

[Marshall Day]

V V,

jfreise has the best answer for you but there are some things you need to know when you are saving "in progress" update sets in preparation for a clone and returning them to the instance.

Remove the condition on the UI Action "Export to XML" to enable the UI Action to show on the "In Progress" update sets.

Export the update sets one by one to a file for later retrieval. It helps to rename them by the update set name to ensure clear tracking.

Unless you want to keep the "Export to XML" UI Action available for all update sets, replace the condition.

Perform the cloning of your specific instance.

Got to Retrieved update sets and scroll to the bottom where you will see "Import Update Set from XML" and select it.

Select the update sets, one by one, to import from your saved file.

Here is where it gets a tad different than other responses.

Once your saved update sets are imported, you will notice that they are in a "Loaded" state.

You must Preview and Commit each update set.

You may have update sets that have errors in the Previewing. You must make a determination as to how to deal with these errors and warnings prior to Committing them.

Communication with the individual developer would be recommended here.

Once Committed and the state is Complete, you can change the state to In progress, allowing the developers to begin working where they left off.

I hope this helps you and any others that are wondering about this important issue.

Marshall Day