When does the Ambiguous Name dialog box for Recipient Name Lookup display?
Under what circumstances does the Ambiguous Name dialog box appear when addressing mail to a recipient in Lotus Notes?
This issue was reported to Quality Engineering as SPR# MNAA8TV5YD and is fixed in 9.0.
Background for previous releases;
Normally, the Ambiguous Name dialog box for Recipient Name Lookup appears if multiple matches of a name are found and any of the following fields are different:
FullName (first value)
AltFullName (first value)
The Ambiguous Name dialog box displays these four fields along with the Location value for each choice to help the user determine which address should be used.
NOTE: Type-ahead functionality has its own Ambiguous Dialog. The difference can be determined by the presence of the above columns.
Determining if the typed name is ambiguous:
1. If there is only one matching name ( Fullname field, first value) in each of the personal and server address books, the Ambiguous Name dialog is skipped.
2. If there is at least one matching name and the four key fields are the same, the Ambiguous Name dialog is skipped.
3. If there is at least one matching name and any of the four key fields are different, the Ambiguous Name dialog displays. The dialog box displays the values of the four fields along with the Location field.
NOTE: The Location column is initially hidden. You must drag a column separator to the left to display it.
4. If the MailAddress field is null in the local Contact Document, then the name is skipped. This occurs when you initially copy the Person Document locally. In this case, the MailAddress field in the local copy is null and is not considered during name resolution.
: If the local contact contains a
MailAddress value (meaning the field is no longer Null), it is now a candidate for ambiguity. However, if one matching name is found at the server and one is found locally, the Ambiguous Name dialog box does not display.
However, this special case no longer applies if there is more than one duplicate on the server. This occurs if the Person Document is copied to another address book that is available via Directory Assistance. This issue was reported to Quality Engineering as SPR# JHOD5LMKWH. The workaround is to eliminate the duplicate name at the server and incorporate any extra information into the main Person Document.
When troubleshooting name lookup, you can add the following lines to the server and/or client's notes.ini file:
Primary names.nsf: DBIndex = 1
Directory Assistance databases: DBIndex = 2, 3, and so on
Directory Catalog: DBIndex = 65535
More support for:
Software version: 6.5, 7.0, 8.0, 8.5, 9.0
Operating system(s): Linux, Windows
Software edition: All Editions
Reference #: 1108944
Modified date: 2013-04-25