Hi all…what is the best practice for creating a user ID with a generational qualifier such as Junior or Senior? I’ve never run across this issue until now. In the NAB Person doc there is a field for generational qualifier but the Register New User dialog in Administrator does not include this field, so presumably it is not included in the ID file.
Our application needs to accurately display the user’s name on documents for “signature” purposes (“John Doe, Jr./My Company”) but it doesn’t pick up the qualifier from the NAB, only what is in the ID.
Should I just include the suffix as part of the last name?
Subject: Generational Qualifier
If you wish for the Generational qualifier to show up in the user ID properties, you must include it as part of the last name… for example:
John Doe Jr
You cannot use any periods or commas in the name.
The entry will appear in the address book as: Doe Jr, John
Subject: that works
Thanks Bradley. I went with your suggestion to add it to the last name.
Subject: Re: Generational qualifier
Some staff insist on having the generational qualifier added to their first name. In your example, this would become John Jr Doe/My Company. They ask for this because a search by their surname, if it is a common surname, would give different results depending on how their account is named.
Another consideration is with how the generational qualifier is treated in other applications such as Active Directory or PeopleSoft. It would make sense to follow, when possible, the placement of the generational qualifier in these other applications.