- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 02:44 AM
Hello,
I'm looking to clone my production instance over my test instance.
I currently have non-committed update sets in my production instance that have already been committed in my test instance. Would it be as simple as recommitting these once the clone activity has been completed?
and will they show in my test instance following the clone from production similar to how they currently show in production (see below)?
I've had to remove the names and description as they are sensitive.
I'm just conscious of loosing work.
Many thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 02:48 AM
Hi Kyren
I guess you will get the un committed update sets also in your test instance available to be committed after clone provided you have not marked the update set table to be ignored in the clone (check the Exclude Table list.). And then it would be as you said 'as simple as recommitting these once the clone activity has been completed'.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 02:48 AM
Hi Kyren
I guess you will get the un committed update sets also in your test instance available to be committed after clone provided you have not marked the update set table to be ignored in the clone (check the Exclude Table list.). And then it would be as you said 'as simple as recommitting these once the clone activity has been completed'.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 03:18 AM
Thank you - I will keep an eye out for this.