Clocing ticket as fixed deployed in the Jan 8, 2018 release as noted in Stakeholder newsletter - Issue 36 RD-4413 Bulk Import Users: Check email address when generating usernames

Work to resolve issue where a CSV file that contains the username (name field) of an existing user appends the username with a “1” or similar number to the end of the username when they org is attempting to update an existing user’s profile fields. Historically and continuing, the name field is not needed when updating a user profile as only the email address field is required, along with the fields to be added or updated. However, there are cases with Org mgrs. using one CSV to create new accounts and do updates simultaneously and populating existing usernames in the name field of the CSV causes this issue to occur. Work in this ticket is creating a method to get the system to ignore the username (name) in the case of existing users and update the user profile where needed should name field be in the CSV.

NOTE: The best practice remains to not use the username (name) field in a CSV. When you run the import you will get a message for those accounts that were duplicate, if any. If you plan to do only one CSV file, omit the name field, allow the system to create the username from the first and last name fields to avoid the “1” or other number in the username for brand new users and use the on-screen message to note your existing users. The exception of course is where the number is warranted. E.g. there are two john.smith users: john.smith and john.smith1

Ticket to Update user alias after changing username in user account form that is causing difficulty changing usernames (RD-4417 - Update user alias after changing username in user account form) is still in progress.

Will close https://globalnetplatform.org/1515399032-kathrynnewton-gcmc as a duplicate