Multiple Users with same first_name and last_name not possible?

Former Member
Former Member
Hello, If I create two users:
<first_name>Joe</first_name>
<last_name>Doe</last_name>
<login_name>joe_doe</login_name>
<first_name>Joe</first_name>
<last_name>Doe</last_name>
<login_name>doe_joe</login_name>
I get the following error: "Identity with Name 'Joe Doe' already exists." Can't we have two Users with the same first and last names in Aras? This seems like a very common use-case to me..
  • Hi Stefan, This is the OOTB behavior when creating two users with the same name, but there are several alternatives that we typically suggest when we hear questions about this.
    1. You can include the middle initial of the user in the first_name property
      1. i.e. John Q. Doe (First Name = John Q.; Last Name = Doe)
    2. You can alter the name of the Alias Identity of the first user to include the login_name
      1. i.e. John Doe [jdoe21]
      2. This allows you to create another John Doe
    3. You append some additional information about the User such as the department they work in to the last name
      1. i.e. John Doe - QA (First Name = John; Last Name = Doe - QA)
    For very large companies where this occurrence may be more common, it would be possible to automate the 2nd option to automatically append the login_name to the name of the Alias Identity when it is created. Chris
    Christopher Gillis Aras Labs Software Engineer
  • Former Member
    Former Member
    Hi Chris, Thanks for your response. Including <login_name> automatically in the <name> won't work with Visual Collaboration or Technical Publication, as these rely on being able to find "Super User" by its name. I guess we could exempt "Super User" from the automation, but is this really the only identity Aras is trying to find in this manner? Will we break something else by including other stuff in <name>? Maybe you can confirm if this is the case? Really appreciate your time, thanks!
  • Hi Stefan, I believe the only other Identity whose name you would need to check for is the 'Innovator Admin', but I would recommend excluding all of the admin Identities just to be safe. You should only need to account for this if you are retroactively setting the names of your Identities. You could also automate this new name format only for newly created Users, so you wouldn't run into this issue with any of the existing administrator users. Chris
    Christopher Gillis Aras Labs Software Engineer