"For customers who are on one of the new license types that were added in October 2019, users must be associated with a license. Users who are associated with a license are automatically added as system users who have no roles the first time that they sign in."
The user ID has a pattern like '$BC8A'. It is a dollar sign with 4 hexadecimal values; which is meaningless and not user friendly when user IDs are presented on forms.
It would be better to have a meaningful user ID. Probably allow a configuration or just take the local-part of an e-mail address. In case of chrisg@contoso.com, the user ID can then be 'chrisg'.
Comments
Its been almost 6 years and nothing on this? THis is a modern day ERP and we cant have userids be custom to logic or allow for non manual intervention when importing users. This is standard stuff in today's IT world and D365 is still stuck with manual processes?
Category: System administration
Why does Microsoft have an Ideas board if they provide no feedback to suggestions? Why does a suggestion made in 2019 not have a single bit of feedback 4 years later? Microsoft, when you ask up to make a suggestion and provide no feedback it is like throwing a "penny in a wishing well". Why bother? Microsoft, are you listening? If you are listening, can you say something. Even an explanation as to why you can't do it would be better than no reply at all. For what it is worth, I threw my penny in this wishing well.
Category: System administration
The proposal is old, but really needed! Could you please improve it.
Category: System administration
I agree with the approach to have a meaningful user ID in case of automatic creation of user account in D365. Currently dynamics create unique user ID with pattern like $####, which is incorrect and not matches with user information. This introduces a manual step to correct this record.
Category: System administration
Suggested point is also something we need to be fixed.
Due to this working, we have to remove manually the automatically user created, import it manually.
For all the personalizations and transactions initially done with such user, it is complex to identify who has entered, approved a transaction.
On our context, it is really key that this feature is enhanced for a better user management (avoid to have manually user creation) and user experience (user name stored having made the transaction not meaningful).
Category: System administration