Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Systemusername Generation Rule is failing

ChaitanyaDesh14
New Contributor III
New Contributor III

Hello team,

We have configured the Systemusername Generation Rule in Global Configuration as follows:

CASE WHEN (users.preferedfirstname!='' OR users.preferedfirstname!=null) THEN concat(users.preferedfirstname,'.',users.lastname) else concat(users.firstname,'.',users.lastname) END ### case WHEN (users.preferedfirstname!='' OR users.preferedfirstname!=null) THEN concat(users.preferedfirstname,'.',users.lastname,1) else concat(users.firstname,'.',users.lastname,1) end ### case WHEN (users.preferedfirstname!='' OR users.preferedfirstname!=null) THEN concat(users.preferedfirstname,'.',users.lastname,2) else concat(users.firstname,'.',users.lastname,2) end ### case WHEN (users.preferedfirstname!='' OR users.preferedfirstname!=null) THEN concat(users.preferedfirstname,'.',users.lastname,3) else concat(users.firstname,'.',users.lastname,3) end ### case WHEN (users.preferedfirstname!='' OR users.preferedfirstname!=null) THEN concat(users.preferedfirstname,'.',users.lastname,4) else concat(users.firstname,'.',users.lastname,4) end


We have uploaded few test users using csv upload and also checked the Generate Systemusername checkbox which uploading. We have observed the following behavior:

1. When the user has a preferedfirstname value, the Systemusername is created as expected( preferedfirstname.lastname ).
2. When the user does not have a preferedfirstname value, the excpected Systemusername is firstname.lastname according to the generation rule set in global config page. But, currently we are getting the systemusername as firstname.lastname1.

Note: In both the cases the identities were unique and none of the users have any systemusername previously configured.

The expected output in the second case should be firstname.lastname, and we are not able to find out why the numeric value '1' is getting appended at the end of systemusername.

Please let us know if we are missing anything here.

Thanks,
Chaitanya.

6 REPLIES 6

naveenss
All-Star
All-Star

Hi @ChaitanyaDesh14 the above conditions are working perfectly fine in my 24.3 instance. Can you please double check if you already have a user with the same systemusername in the system?

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

rushikeshvartak
All-Star
All-Star

It was working before ?

Could you kindly provide a detailed snapshot of the information extracted from the logs, encompassing errors and other pertinent functionality details encountered during the execution of this process? Your assistance in furnishing this information would greatly aid in the analysis and resolution of any issues .


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

ChaitanyaDesh14
New Contributor III
New Contributor III

Hello @naveenss  and @rushikeshvartak 

We inserted a new user 'AD.Test31' for this testing.

Here is the output of the data analyzer showing it is a unique user.

ChaitanyaDesh14_0-1716201599293.png

The desired username and systemusername should have been 'AD.Test31', but for some reason it has appended another '1' at the end of the username and systemusername.

Here are the user details:

ChaitanyaDesh14_1-1716201712841.pngChaitanyaDesh14_2-1716201745983.pngChaitanyaDesh14_3-1716201765839.png


Please let us know why is the system adding another '1' to these username and systemusername fields.

Thanks,
Chaitanya.

NM
Regular Contributor III
Regular Contributor III

Hi @ChaitanyaDesh14 , check once if any user have  same systemusername?

Can you share logs. It will print query which is used for generating systermusername


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

ChaitanyaDesh14
New Contributor III
New Contributor III

Hello Team,

The issue is not coming up anymore and we are getting the expected results without doing any changes to our configurations. We were previously testing this while working on version 24.2.

But now after our upgrade to version 24.5, this config is working fine.

Thank you,
Chaitanya.