Constituent Merge in v11

According to our users, in v10 accounts scheduled for merge would merge even after some minor update (non transactional)  in between the time accounts schedule for merge and merge procedure could run but in v11 they won’t; any minor changes in delete or keep account after they scheduled for merge will prevent them from merging. Does anybody know if there is any changes regarding this in v11 merging procedure? I couldn’t find  anything in the v11.0.4 release notes. Thanks for any information on this.

 

Mo

National Ballet of Canada

Parents
  • After years and countless merges being delayed by a day due to just such trivial, non-transactional updates, we realized that these "Merge aborted! Reason: Customer activity took place..." errors had never resulted in a merge being skipped that we actually wanted to skip. So, we commented out the block of code in AP_MERGE_CUSTOMER that does this particular check, with no regrets and less wasted time. YMMV...

Reply
  • After years and countless merges being delayed by a day due to just such trivial, non-transactional updates, we realized that these "Merge aborted! Reason: Customer activity took place..." errors had never resulted in a merge being skipped that we actually wanted to skip. So, we commented out the block of code in AP_MERGE_CUSTOMER that does this particular check, with no regrets and less wasted time. YMMV...

Children
No Data