Body: <p>I'm not even certain how best to ask this question. Here's the situation:
  Staff people at an org I support often wind up accidentally creating duplicates of themselves during event testing in Civi but with incorrect or empty name fields (and other fields).</p>
  <p>Whatever system Civi uses to de-duplicate emails, these empty records often wind up being the ones that get selected when emails go out which leads to folks receiving &quot;customized&quot; emails with empty data where a token fails because there is nothing in the name field. This also sometimes happens for non-staff records if we import a list from somewhere else that has no names but duplicates an existing email. Obviously we want to reduce and eliminate duplicates, but we can't necessarily take time to do that before every email.</p>
  <p>I'm wondering if there is some way to manage priority when CiviCRM is doing its de-duplication during a mailing to ensure that our &quot;canonical&quot; record comes up rather than some recent import or unwisely created duplicate without good data. Is it possible to get it to always favour the lowest value CID, or something like that?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-18T21:32:07.410Z
Comments.Text: I saw a comment recently about a Job that could rerun the default bulk duplicate merging - wondering whether you need something like that running on your system
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-19T17:14:06.823Z
Comments.Text: That would certainly help limit the problem. I'll see if I can turn up that note. Was it here on StackExchange?
Comments.UserDisplayName: kapn
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-22T02:49:08.130Z
Comments.Text: actually i can't find it - thought it was a discussion on MM - if you post there I will @ the person i thought mentioned it
Comments.UserDisplayName: petednz - fuzion
Tags: <civimail><duplicate-contacts>
Title: Possible to set a contact as the default for a particular email
ThreadText: # Possible to set a contact as the default for a particular email
  
  (Asked by: username_0 on 2024-01-18)
  
  I'm not even certain how best to ask this question. Here's the situation:
  Staff people at an org I support often wind up accidentally creating duplicates of themselves during event testing in Civi but with incorrect or empty name fields (and other fields).
  
  Whatever system Civi uses to de-duplicate emails, these empty records often wind up being the ones that get selected when emails go out which leads to folks receiving "customized" emails with empty data where a token fails because there is nothing in the name field. This also sometimes happens for non-staff records if we import a list from somewhere else that has no names but duplicates an existing email. Obviously we want to reduce and eliminate duplicates, but we can't necessarily take time to do that before every email.
  
  I'm wondering if there is some way to manage priority when CiviCRM is doing its de-duplication during a mailing to ensure that our "canonical" record comes up rather than some recent import or unwisely created duplicate without good data. Is it possible to get it to always favour the lowest value CID, or something like that?
  
  **Tags:** civimail, duplicate-contacts
  
  > **Comments:**
  > **username_1**: I saw a comment recently about a Job that could rerun the default bulk duplicate merging - wondering whether you need something like that running on your system  
  > **username_0**: That would certainly help limit the problem. I'll see if I can turn up that note. Was it here on StackExchange?  
  > **username_1**: actually i can't find it - thought it was a discussion on MM - if you post there I will @ the person i thought mentioned it  
  
  ---
  
  ## 0 answers
  
  