If an import job is configured to make new phones/emails/addresses primary "Only if the constituent has no address/email/phone", the logic doesn't hold when resolving potential duplicate matches. Because the default action in those cases is "Insert" (and only changes to Update once you select one of the offered matches), the primary flags start as "True". The problem is that they stay True even after selecting to update one of the offered constituents instead. It would be much preferable if the primary flags knew to change to False if the selected constituent already had another contact on file, similar to how "Insert" will automatically change to "Ignore" or "Update" (based on settings) when the chosen match has the incoming phone number/email/address already on file.

The current process requires manually going to each tab and changing the primary flags to False if there is already a phone/email/address on file for the selected constituent, and we are sometimes resolving hundreds of potential duplicate matches for a single import job, so it's a time-consuming oversight.