Hi chunheng

That would be a complex development on a sensitive topic (security related). I don't understand why the customer would like to do that anyway. A code is a code, the meaning is in the description and the login is what the users will type in. If a women got married and change her name, how to update the family name, do you end-up creating a new user?

I advise your customer to stick to the standard.

Hi chunheng

That would be a complex development on a sensitive topic (security related). I don't understand why the customer would like to do that anyway. A code is a code, the meaning is in the description and the login is what the users will type in. If a women got married and change her name, how to update the family name, do you end-up creating a new user?

I advise your customer to stick to the standard.

Hi Julien,

Was reading this LDAP auto-user population document and I had a concern when the login name was similar (for example, a twins employee with same starting 5 character name like Cheng): https://www.sagecity.com/gb/sage-x3/b/sage-x3-uk-support-insights/posts/ldap-and-classic-users and https://www.sagecity.com/us/sage_x3/b/sageerp_x3_product_support_blog/posts/how-to-set-up-automatic-sync-for-ldap

Seems like Sage X3 LDAP service will create with a randomized code if matching first 5 characters are found: www.sagecity.com/.../ldap-user-sync-x3-user-creation-x3-user-code-should-be-ad-property

As such, this question has been resolved.