Good day all,I have read and re-read the many posts on the type-ahead and the Recipient Name Lookup features of Notes and could not find a solution to my problem.
We are using Directory Assistance and have several address books. Some of our users always use the Employee address book (Not the NAB) for addressing mail. They do not want to use the type-ahead feature or recipient name lookup. They simply want to pick the recipient name from the address book they need to use and send mail to that recipient. If a name picked from the Employee address book also happens to exist in the local personal address book (but with a different e-mail address) the mail is sent to the address in the personal address book regardless of where they pick from. We do not want the “Ambiguous Name” window to appear since the user is picking the recipient they want. What I need to do for these users is turn off “Recipient Name Lookup”, but the only options are 1. Stop after first Match or 2. Exhaustively check all address books.
We had the same problem. More specifically sending to the wrong person. On the Location document, I’ve selected “Exhaustively Check All Address Books”. This will prompt the user with duplicate names.
Hmmm… tough one. The local address book contains the location information they need in order to connect to the server, so you can’t disable it’s lookups.
Then you have people who keep contacts locally with home addresses and phone numbers that are different from those in the NAB. So, if you added an agent that would update users from the NAB into the local, it would/might overwrite information that they want to keep.
Adding a few agents that will update entries in the local address book from the Employee Address Book or NAB might help, if the
user is diligent about keeping up their local address book.
If it makes you feel better, I had to go to individual workstations and delete invalid entries in the local address books, and ended up writing an automated module to update names in the local from the multiple NABS. That was a good excuse to spend time with a few employees and review how to use the local address book.
Perhaps a training class? See if you can’t get your HR department to sponsor it.
The cleanest solution would be to distribute a condensed dircat to all users’ local machines (via desktop policy, natch), remove all redundant entries from all users’ local perNABs, and wave a magic wand which prevents users from ever again copying an address from a publix address book to their perNAB.
This might not alleviate all dupes, but this in combination with the “Exhaustively check” option is the best, I think, that you’re going to get.
They’re special-order only, and the waiting list is very long. However, a couple of guys in sharkskin suits who wander from desk to desk reminding users of what a nice home they live in and how it would be a shame if it were to burn down might prevent duplicating entries. And they can be rented at a reasonable cost. Of course, they may want you to return the favour some day…