I am noticing that the email that is shown in the dupe match results is actually just the first email on the record instead of the email that was matched.
For example, if I have a record in RE with the emails (in this order):
If I import the email email@example.com I will get a dupe match that shows it is an email match, and it will display the incoming email address, but on the record line it will only show firstname.lastname@example.org instead of the email address that was matched.
This is especially difficult because the same "email match" icon can show up if the email is on a relationship record for example.
Doesn't it make sense to show that the email that was matched is on that record? Especially if it is of the same type as the import profile says.
I think you'll see that after the issue with the email/phone always showing the first entry is resolved, the results screen will in that scenario, more accurately reflect a match.
The behavior you are seeing for Addresses was changed in version 2.4.
From the Revision History:
- Updated duplicate search screen to always display the best address match instead of always showing preferred
You can download version 2.4 here: http://omaticsoftware.com/Forums/tabid/108/aft/1067/Default.aspx
That is not the behavior I am seeing.
Take the following example (image 1):
This is a Test: email@example.com
Spouse Test (non-con spouse): firstname.lastname@example.org
Row1 (image 2): Name: This is a Test, Email: email@example.com
Row2 (image 3): Name: Spouse Test, Email:firstname.lastname@example.org
In the first match screen, the match is an email match because phone and email searching does not exclude spouse relationship phones, however its not showing the actual email address it matched on - which is the display behavior I have filed to have changed.
The icon is correct because it matched on the primary constituent's name, and the spouse's email address. If you did not have an email address in the file, the results returned to you should be the same, but there would be no icon because there isn't one when a primary constituent is matched only by name and address (versus a spouse match on name).
In the second match screen, the match is on the name of the non-constituent spouse, as well as an address, which ranks higher than the email match for the record the non-constituent spouse exists on, therefore the icon is the one that indicates the match is on the spouse relationship record.
In your screen shots above, with the exception of the actual matching email address not being displayed in the grid, IOM is functioning as designed.
Can you remind me what IOM version you are using, please?
Thank you for the information!
I have been able to duplicate this behavior, and after some additional testing I have been able to determine what is happening. IOM is matching on the correct email address, but it is displaying the first email address in the actual table (not the grid on the record) for that Constituent.
I will file to have this display behavior changed in a future release.
Having IOM display the actual email address it is matching on, in the grid, is the change I am filing.
The icons used to indicate the type of match are displayed based on a hierarchy coded into IOM. The icon for an email address match ranks below the icon for a non-constituent spouse match. So if both data points are matched, the non-constituent spouse match icon is the one that will display in the grid.
Regarding also displaying the Type in the grid: I will file that as a Feature Request. IOM does not evaluate the Type at all in this part of the process (matching to the Constituent, versus updating the email address data), so I can't predict if Development will add that to the display grid. You might want to file it on User Voice, too!