How to fix it

  1. Navigate to System Update Sets > Retrieved Update Sets and open your update set.
  2. Click Preview Update Set to see all collisions and errors before committing changes.
  3. For preview errors (missing dependencies): note the missing tables/fields, then load and commit the dependency update sets first before retrying.
⚠️

Always resolve preview errors before addressing collisions — missing dependencies will cause failed commits.

  1. For collisions, click View Update on each colliding record to see the XML diff between source and target versions.
  2. Compare timestamps: check sys_updated_on values in the XML to determine which change is newer — incoming (source) or current (target).
  3. Choose resolution:
    • Accept Remote = take the incoming change from source (overwrites target)
    • Skip = keep target version (ignores incoming change)
  4. For business rule and script collisions: manually merge the logic by accepting remote, then editing the record post-commit to include necessary target-specific changes.
  5. Click Apply Remote Update or Skip for each collision based on your analysis.
💡

Document your collision resolution decisions in the update set work notes for future reference.

  1. Once all collisions are resolved and no preview errors remain, click Commit Update Set to apply changes.
  2. Monitor the commit progress and check for any runtime errors in System Logs > System Log > All.
💡

Verify the fix by testing the modified records' functionality and checking that business rules fire correctly.