Unable to move an update set with missing records because the customer updates are in a different update set/scopeIssue An update set with missing records could not be committed because the customer updates are in a different update set/scope. A common preview error is: "Could not find a record in <table_name> for column <column_name> referenced in this update"CauseThe solution will depend on the type of changes that were made. In most cases, it is best to create a new update set in the correct scope and re-do the changes to ensure all records, related records/special handlers are within the new update set.Once the new update set has been made, you can: Merge it with the original update set and commit that, orDepending on the type of changes that are the missing records, skip the missing records to commit the original update set then commit the second update set that contains the corrections.ResolutionResolve a preview problem with an update set.