Preserving implementation done on lower environment after cloning from prod

[Dhana3]

Hi Everyone,

I need solution approach ideas from you all.

We have few implementations that are only present on our lower instances like data sync from prod to lower instances. The data import is done via scheduled data import.

When we clone from prod to lower instances, we have to manual take the backup of those update sets and commit them after the clone. Can you suggest an solution approach so that this manual backup and recommiting is not required?

So far I was suggested 3 approaches:

1. Moving the application to dedicated application repository (all the implementation belongs to Global scope)

2. Adding the table to data preservers

3. Creating a post-clone script and committing the update set via script.

Please suggest any other solution approaches as well, if you have implemented anything similar on your environments.

Thanks,

Dhanashree

[brianlan25]

Make sure your update sets are in the in progress state then set the following when you create your clone.

[Dhana3]

Hi brianlan25,

Will this preserve the implementation or do we have to re-commit the update sets? We are looking for a solution that will not require manual intervention, because it is likely that we will forget about it.

[brianlan25]

I'm not 100% sure and the explication on docs does not make it any cleaner. 

"Preserves the last 90 days of in-progress update sets in the global application scope. This option allows you to keep in-progress, global update sets created within the last 90 days on your target instance."

I have yet to try it as my project manager know the importance of clones especially during upgrade and keeps any new development in the backlog.

[brianlan25]

I just watched a video I noticed at the top of the page. It didn't mention the the preserving in progress update sets and said specifically that if you want to keep development that you did not commit to prod you either should export your update sets for sync to git for scoped apps. Its almost like there admitting they have a setting that doesn't work.