Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-20217

phone based dedupe rule fails to match when importing

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.7.16
    • Fix Version/s: 4.7.27
    • Component/s: Dedupe
    • Labels:
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Needs Funding
    • Verified?:
      No

      Description

      If:

      • you create a dedupe rule that just matches on phone number.
      • do an import with a record that has a phone number matching a phone number of a contact in the database
      • specify that you want to update on duplicate match
      • specify the phone number only de-dupe rule

      Then... the new record will be imported and will not match the existing record.

      That seems to be because it will be imported matching the "phone" field - but the dedupe rule is looking for the phone_numeric record.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jamie Jamie McClelland
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: