I noticed what I thought was some odd behaviour in our merges so I had a look at the stored procedures and found LP_CONST_MERGE which is brief, but references AP_CUSTOMER_MERGE. I couldn't find AP_CUSTOMER_MERGE so went to the documentation to see if I could get a bit of background. I've found this;
"To prevent a specific constituent record from ever being merged with another constituent record, a Void Merge attribute can be added to the record with the value set to Yes:
When this attribute exists on an account with a value of Yes it cannot be merged with another record; the record cannot be the Keep ID or Delete ID in a merge. There are no exceptions to this behavior."
Am I imagining that this is not how it used to be in V10? I'm sure that we could have a 'Void Merge' on the KeepID and it would work? Also, I spent quite a while getting various warning messages to display if you tried to schedule a merge that was going to fail and it seems that these no-longer display either.
Can anyone shed any light?
Thanks, Suzanne
No, it has always been like that, it has always stopped any merge if the VOID Merge attribute is set to Yes on either record.
Caryl
Thanks Caryl, I don't know why I thought that it worked before. Maybe I had managed to alter the procedure. Unlikely!
I'll be interested to see if anyone else has had warning messages disappear.