SystemUserName Generation Behavior

[raghuraghav]

We have our own logic of building the systemusername for an user based on the employee type. What we are observing is that even though the system username generated is unique in the users table, it  looks if there is an same name in Accounts table, the system username is not getting assigned.

For example if we have created a system username of ABC12345 and there is an orphaned account from one of the end points with ABC12345, then the system username is not being assigned to the user.

SystemUserName ABC12345 exists in Accounts name so ignoring rule

Is this the behavior of not able to assign a systemusername even though its unique from users perspective and it exists in the Accounts name?

[dgandhi]

This shouldn't happen as uniqueness should be within the users table and not across accounts table.

Thanks

[vikyjain]

if your account name rule is users.systemusername = accounts.name and if an existing account (orphan or not) exists already with the same name, then the account name rule will fail it wont automatically assign but, if we have an account correlation rule setup, orphan accounts can get attached to the user depending on connector type need to understand the use case here

[raghuraghav]

The use case is we are trying to create a new user and have the system username generation rule to assign a systemusername during creation. What we observed is that, the system user generation rule is fired and it generates the systemusername as per the logic for a user, however since the created one exists in the Accounts table, this is not getting assigned and the message is seen in the log files. When we update the logic to a have a unique one all together.. start from ABC20000, it works fine. Hence the question of what is the expected behavior here. The systemusername generation rule checks for uniqueness in the users table or across all the data including accounts.