Updates in an update set no longer uses sys_updated_on time of an update to determine changesIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Previewing an update set displays a message in preview problems indicating that there is a local change which is newer than the change from the remote update setReviewing the actual local update on the target shows that the changes are actually older than what is being brought over from the source based off of the sys_updated_on field CauseThe behavior for this is expected as there has been a change in the update set engine where we are no longer using the time of an update to determine whether or not changes have been made. The logic used now is more in line with source control practices. Any update set that is being brought over from a source instance to a target instance will always produce a collision error if there changes were made to the same record in both target and source instances regardless if the changes on the target is newer or older than the updates on the source. The engine now treats this as a merge conflict similar to what is seen with source control.ResolutionThe user, administrator, or developer needs to determine which changes to keep and then apply these as needed.