Update set carrying old updates in Production

[Ankita NA]

Hie Team, I am in need to get cause related to below issue.

1. I move one update set carrying 14 updates from DEV to UAT via XML and committed it.

2. In UAT I made that update set In Progress and captured some more customer updates related to Catalog Category and I had to make few catalog items inactive too. So now total customer updates in UAT became 28.

3. There was some ECR on 29th and as my update set was in complete state and has 28 customer updates got loaded to PROD to via update source.

4. on 30th I made my update set In Progress again in UAT and removed 7 extra updates which were not under my story by mistake it got captured.

5. After that my Update set had only 21 customer updates and it was it was in complete state

6. On 31st when data was loaded via update source to PROD, and my update set was committed it was not updated as it still had 28 updates in it instead 21.

So, want to ask what the possible reason for it could be. 

Though I know that we should not be adding changes direct to UAT, but some data was missing in DEV that's why to capture those I had to reopen my update set. Please suggest if anyone has encountered this type of issue while working.

Thanks,

Ankita

[Dnyaneshwaree]

Best practice: Do not make any update to "in progress" ones it gets completed and migrated. Instead of this we can make new update set for new updates in dev and after capturing all the updates we can merge new and load update sets into single new merged update set and then we can migrate that into UAT and after testing same will migrate into prod.

For your case, after removing the unwanted updates you need to check that all the updates are removed successfully and there is no any dependencies for those and no committing errors after committed it into prod.

If my solution helps you any way then mark it as accepted and helpful.

Thank You!!