Update a person's last name

Owned by Craig Savino
Nov 08, 2022
2 min read

 

Update the login at the OS/Network level.
 
Update the SQL database:
Check SQL for authentication mode. If you are using SQL authentication you will need to add the new UserID. If you are using Mixed Mode no changes required.

Update the person’s name in Colleague:
In UI change the name of the person on the Name and Address Entry (NAE) form as appropriate.

Update the person’s UI login ID: 
In UI, you will need to modify the person’s UI login ID: Create a new Operator (also referred to as OPERS or UT.OPERS) record for the user that is a copy of the old one.

An easy way to do this is to pull up the user's current record on the Operator Definition (SOD) form in one UI session, and in a new UI session go to SOD, add a new Operator record, and manually enter all of the same information as you see on SOD for the original. Remove the value from the “Org Entity ID” (person.id) from the original SOD record, and put it onto the new SOD record. 
 
Update the person’s STAFF record in Colleague:
In UI on the Staff and Volunteers (SVM) form, pull up the person record and change the Staff Code and Operator ID from the old to the new operator code. 
 
Update the person’s web user login:
In Colleague UI, you will need to update the WebAdvisor login:  Change the Person User ID on the DMI Registry User Setup (DRUS) form.

First, check ‘DMI Defaults’ in SA Valet to see what ‘LDAP Synchronization’ you are using. 
If you are using an LDAP synchronization level of 1 or 2 then the login ID should be changed on DRUS first and that will also change it in Active Directory.  
If LDAP synchronization is not being used then the name can be manually changed in Active Directory and then changed on DRUS.

NOTE: If you want the User ID on DRUS to be calculated based on your Web User ID and Pin Options (WUIP) run the Delete Web User Registry (DDRU) process prior to DRUS. Otherwise, what you enter on DRUS will be a manual entry.

Update the Resource DB (ORG.ENTITY) with the change:
Run the Export Person to Resource DB (EPDB) process to push the updated name into the resource database.
 
WINDOWS CLIENTS: You will most likely need to reboot your application server in order for the change to be implemented. Please see document 000005727 (4202: R18 SQL: User Name Change - Old User Name still showing up). It basically states that Windows caches an old user's login ID even after it is changed. In order to clear this cache for Windows and have the new login ID be used, the Application server needs to be rebooted.

 

Additional Information or Related Articles

 

 

PORTAL CLIENTS: Please see 000002081 - 7409: Handling Name/UsernameChanges in the Ellucian Portal