Update set issue while moving to higher instances

[Jagan Pillutla]

Hi all,

I have encountered a problem when moving the update set from dev to test and to Prod. Let me give you a brief background about the issue: I have been working on a kind of mini project (end to end responsibility is mine) and the 

Update set has 600 customer updates. This task involves creating a catalog item, custom tables,many sub flows under a single flow (flow designer) and so on. While it is moved to test instance, faced with many errors, accepted all the remote updates, but after committing the update set the catalog form behavior has totally changed, there were couple of variables missing, UI Policies and Policy actions missing. So created a new update set and captured the missing things and committed in the test again, then it was working as expected. Finally when it is time to MTP while committing the update set, as expected faced with too many errors, accepted all the remote updates. After committing and while validating, I can see only flows and one custom table (It's supposed to be 2 tables) in the PROD instance. 

It all happened just before the cloning activity (MTP and dev cloning were coincided, irony !!). Dev got cloned with PROD and all the hard work that I have done for months is wiped off in dev instance . A small relief in this storm is that I have taken back up of the update set (xml) from dev before moving it to test and Prod.

My question here is, if I can use the back up update set in dev and finish the missing parts in PROD and move it to higher instances or should I take update sets from test or Prod and use them in dev to continue the development. I am really struck here.

I don't know if I articulated enough to make my case fathomable. If I did, could any one please help me with this? 

Thanks in advance !!

[Ahmmed Ali]

Hello @Jagan Pillutla 

Since you are getting issues in Prod and your dev is recent clone of prod, I would take update set export from prod and deploy that to Dev, so that now prod and dev will be same. Then work on the missing configurations and capture those in new update set and move that new update set/s to test and production.

If you have any sandbox instance, then you can deploy your Dev update sets (which has all updates) in that sandbox to compare the configurations.

Hope this helps.

Thanks,

Ali

[maine2]

Know first, what's the effect of this issue in PROD instance? Then decide if you can revert the changes or not.

Assuming that other instance, temp or stage(or clone from PROD in any of these instances), have the same issue as PROD, If you are able to capture which update sets are missing, better to recapture it and moved it to that instance then test again before moving to PROD.
As much as possible don't fixed it directly in PROD unless it's just simple changes.
 
Assuming again that you have different updatesets from different catalog, table or some of the action, when moving this in higher instances, sort it first from oldest to newest.

[Jagan Pillutla]

Hi @Ahmmed Ali ,

Thank you for your swift reply !t

I have lot of rework to be done in that case