While moving update set if conflict ocures then what to do?What is the best practice to overcome this?

[manojpanda]

Hi Developers,

While moving update set if conflict ocures then what to do?What is the best practice to overcome this?

[lks]

Review those conflicts and that will help you decide weather to commit or skip it. That is the only best practise 🙂

Thanks, Lalit

[manishasharma]

HI Manmat,

After previewing any update set if the update set preview problem comes out to be as Collision, then it means the target system has found a latest update on an object which is newer than the changes captured in update set. Or change in the update set is older than a change to the same object on local instance.

This type of issue generally happens, when we update any script in target instance (lets say hot fix), and don't apply the same change in other instances. Due to this both instances (scripts/or other changes) losses their sync   and results into collision during update set transfer.

Resolution:

You can fix it by comparing the two versions and find out which one is needed.

If you need the version of local instance- then select Skip remote update. Because we don't need the change which is coming via update set.

If you need the version in the update set-> then select Accept remote update, this will consume the change captured in the update set.

Below actions help to identify the problem:

• Compare with local: opens the preview record, which provides a comparison of the differences between the local version and the version in the Update Set.
• Show local field or Show local record
• Show local update

You can refer this link to know how to address other type of update set transfer issues. Resolve a preview problem with an Update Set

Thanks,

Manisha

PS: Please Hit like, Helpful or Correct depending on the impact of the response

[lks]

Very detailed explanation Manisha, much appreciated!

[manojpanda]

super explanation, thanks Manisha