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
Hi Mo -
I had this exact same 'huh?' moment earlier this year. This is what was determined (from Tessitura):
------
Merge pairs will be skipped if the value of the Last Activity Date is after the date on which the merge pair was identified. The date the pair was actually scheduled does not come into play in this process.
It makes sense that we would use the date on which the merge pair was identified, because so many organizations do not check each merge pair when merging customer records. Often, organizations only check segments of their database - major donors, VIPs, subscribers, etc. If you are not checking most of your records, you would want your merge pair to be skipped in the case where activity has taken place. For example, the customer name could have been changed.
Now I thought maybe I was not remembering how it used to be correctly, and it had always been like that. But if other people noticed the same change, maybe I am not so crazy after all.
Anywho - there's the scoop. The official 'why' of the matter.
HTH,
Heather