Add a Clear Results function to the Constituent Merge Process and/or safeguards to prevent data issues if the merge process fails

My organization had a Constituent Merge Process terminate unexpectedly, likely running into our app pool recycle. Though the process indicated there were 0 records processed, thousands of records were left partially merged without us knowing, causing data issues when we reran the process. To prevent this issue in the future, we would like to have a Clear Results function added to the Constituent Merge Process or a clean abort safeguard on the constituent merge process so that records aren't left partially merged.

Another change we would like is an accurate count of the number of records that were affected in a failed constituent merge process. If anything has been processed on the merge pairs, even in a failed run, it can mess up the data the next time it is run, so we'd like to have a way to see the merge process failed but partially processed records so that we can review the tables before re-running the process.

  • Guest
  • Apr 10 2020
  • Reviewed: Voting Open
Organization Name (Please enter full organization name) US Fund for UNICEF
Reported Version 4.0
  • Attach files