Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEMSSPRT-376: Fix Duplicate Contact Detection #72

Conversation

shahrukh-compuco
Copy link

@shahrukh-compuco shahrukh-compuco commented Jan 20, 2025

Overview

This pr fixes the detection of duplicate contact. Prior to this pr if a dedupe rule used email field for detecting duplicates then it did not work if the duplicates were between the contacts other than the first contact as the email for first contact is saved at the time of validation but for other contacts the emails are saved at the end after all the contacts have been created and for this scenario two different contacts were getting created through webform submission even if they have same dedupe rule fields. This pr fixes the issue and now the duplicate contacts are detected successfully.

core pr: colemanw#1033

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@jamienovick
Copy link

jamienovick commented Jan 20, 2025

@shahrukh-compuco

"if a dedupe rule used email field for detecting duplicates then it did not work and two different contacts were getting created through webform submission"

  1. When you say, "if a dedupe rule used email field for detecting duplicates", do you mean any rule which included using email, or only rules which are email only?
  2. This sounds like it would be a big issue, do you know when it started? I'm sure this worked in the past...
  3. Are we fixing this in the core module and sending PR? Just again, it seems so big/fundamental that I'm wondering how its not been found before!

@shahrukh-compuco
Copy link
Author

shahrukh-compuco commented Jan 21, 2025

@shahrukh-compuco

"if a dedupe rule used email field for detecting duplicates then it did not work and two different contacts were getting created through webform submission"

  1. When you say, "if a dedupe rule used email field for detecting duplicates", do you mean any rule which included using email, or only rules which are email only?
  2. This sounds like it would be a big issue, do you know when it started? I'm sure this worked in the past...
  3. Are we fixing this in the core module and sending PR? Just again, it seems so big/fundamental that I'm wondering how its not been found before!

@jamienovick

  1. I mean any rule that included email field
  2. I checked to find out when it started but I dont see any such commit that could introduce this issue, but there is one thing worth mentioning that it will work fine if the duplicate is between contact 1 and other contacts but if the duplicates does not involve contact 1 then it would be an issue as the email for first contact is created at the time of validation but for other contacts the emails are saved at the end after all the contacts have been created already.
  3. Will check on this with the team as I am not sure that we are sending the prs to this core module or not

@jamienovick
Copy link

Could you update the description to make 2 clear?

@shahrukh-compuco
Copy link
Author

Could you update the description to make 2 clear?

done

@shahrukh-compuco shahrukh-compuco changed the base branch from 7.x-5.8-patches to 7.x-5.8-patch6-rc February 10, 2025 07:23
@shahrukh-compuco shahrukh-compuco merged commit e703116 into 7.x-5.8-patch6-rc Feb 10, 2025
@shahrukh-compuco shahrukh-compuco deleted the femssprt-376-fix-duplicate-contact-detection branch February 10, 2025 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants