Duplicate record not found when using Everydayhero Integration and selecting First name in the Constituent Matching
We have evaluated this issue and have determined it will not be addressed in the program in its current state. In this case, we believe the risks and challenges outweigh the potential benefit of resolving this issue. We strive to select the most impactful changes and issues to address with each release to accelerate the rate at which we deliver new features while sustaining the highest level of quality for our customers.
Alternate solution 1. Adjust the Everydayhero duplicate criteria: Setting, constituent matching to use Email address instead of First Name 2. Monitor Everydayhero imports for duplicates. Users should manually merge or use the Duplicate Constituent Management Tool to assist with addressing potential duplicates caused by this issue.