Update set in different upgrade versions

[Suresh Kumar8]

Hello Developers,

I have a question regarding the update sets.

1. I created one update set in dev instance (Washington DC) and completed and committed the update set in YOKOHAMA version. My production is in (Washington DC). If I move the update set from dev to prod now, will the changes be moved?

2. I created one update set in dev instance YOKOHAMA version and committed in it same version. My production is in (Washington DC). If I move the update set from dev to prod now, will the changes be moved?

Will there be any impact on this?

Thanks,

Suresh

[Anurag Tripathi]

1) YEs, no issues

2) There may be some issues going form a higher version to lower version, depends on product and objects touched. 

[Brian Lancaster]

This should answer you questions.

Retrieving and committing update sets between different versions or patch levels - Support and Troub...

[Dr Atul G- LNG]

Hi @Suresh Kumar8 

1. I created one update set in dev instance (Washington DC) and completed and committed the update set in YOKOHAMA version. My production is in (Washington DC). If I move the update set from dev to prod now, will the changes be moved?

Atul: Theoretically, it’s not an issue, but it could create problems if there’s something you change that works in Yokohama but doesn’t exist in the D.C. release. In that case, releasing the update set could cause issues.

2. I created one update set in dev instance YOKOHAMA version and committed in it same version. My production is in (Washington DC). If I move the update set from dev to prod now, will the changes be moved?

Atul: Same as above.