Attributes are not deleted from the source constituent’s record after merging duplicate constituents.

The Constituent Attributes Merge Task is designed to work as follows:
 
One-per Record Attributes
If the target does not have a one-per-record attribute and the source constituent does have one of that type, the program copies the source’s one-per-record attribute to the target.
 
Duplicate One-per-Record Attributes
The program does not allow constituents to have one-per-record attributes of the same type. If the source and target have attributes of the same type that only support one attribute per record, the merge task excludes the source’s attribute. If the merge task excludes a source’s attribute, it deletes it from the source.
 
CRM users may notice that constituent attributes remain on the source constituent’s record after merging duplicate constituent records.  
We are currently evaluating this issue and will update this article when we have more information.

Environment

 3.0.516.28

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.