PARTNERS - Please join us for our upcoming webinar:
Leveraging Intelligent Recommendations for Operational Transformation.
AMS Partners click HERE | EMEA/APJ Partners click HERE

Not able to create username while import

rohanpandit
New Contributor II
New Contributor II

Hi Team,

We are getting error while creating a user via  import Job. We are creating username  from Saviynt only while importing a user from Successfactor. We are getting validation error. Please check.

 

2024-05-09T17:15:09+05:30-ecm-worker-services.ImportSAvDataUserService-quartzScheduler_Worker-1-vn54c-ERROR-Error in saving user username:null :: employeeid : xxxx
 
2024-05-09T17:15:09+05:30-ecm-worker--null-vn54c--grails.validation.ValidationException: Validation Error(s) occurred during save():
 
2024-05-09T17:15:09+05:30-ecm-worker--null-vn54c--- Field error in object 'com.saviynt.ecm.identitywarehouse.domain.Users' on field 'username': rejected value [null]; codes [com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.error.com.saviynt.ecm.identitywarehouse.domain.Users.username,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.error.username,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.error.java.lang.String,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.error,users.username.nullable.error.com.saviynt.ecm.identitywarehouse.domain.Users.username,users.username.nullable.error.username,users.username.nullable.error.java.lang.String,users.username.nullable.error,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.com.saviynt.ecm.identitywarehouse.domain.Users.username,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.username,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable.java.lang.String,com.saviynt.ecm.identitywarehouse.domain.Users.username.nullable,users.username.nullable.com.saviynt.ecm.identitywarehouse.domain.Users.username,users.username.nullable.username,users.username.nullable.java.lang.String,users.username.nullable,nullable.com.saviynt.ecm.identitywarehouse.domain.Users.username,nullable.username,nullable.java.lang.String,nullable]; arguments [User Name,Users]; default message [Property [{0}] of class [{1}] cannot be null]
 
 
rohanpandit_0-1715256195343.png

 

16 REPLIES 16

Raghu
All-Star
All-Star

@rohanpandit  what is username you expecting may i know ? give some example please?


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

rohanpandit
New Contributor II
New Contributor II

@Raghu on the basis of first and lastname. PFB example.

rohanpandit_2-1715265692174.png

 

NM
Honored Contributor
Honored Contributor

Is it like working some and failing for others?

NM
Honored Contributor
Honored Contributor

Hi @rohanpandit, is user first name and last name empty?

rohanpandit
New Contributor II
New Contributor II

@NM it's not empty. Attaching postman Screenshot.

 

rohanpandit_1-1715265571518.png

 

NM
Honored Contributor
Honored Contributor

Can you share import job ss once.

rohanpandit
New Contributor II
New Contributor II

Attaching screenshot. @NM 

rohanpandit_0-1715266032450.png

rohanpandit_1-1715266104312.png

it's not working for all. If i import username from successfactor then it will work but this is not the usecase for us as username generated in successfactor is not correct.

Also this was working before, it is stopped working suddenly.

@rohanpandit : You cannot generate username using the setting you have shared from Global Configuration -> Identity LifeCycle. This will come into picture for users created through Saviynt UI/API.

If you want to generate username as part of import then use inline preprocessor and map it to username. Because username is mandatory mapping as part of import so during import only you have to assign username either by directly mapping any of the attribute from target or generate using inline preprocessor logic and assign it to username column of saviynt. 


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

  • How are trying to create user ?

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

@rushikeshvartak  via import Job.

Username is mandatory attribute and you can't compute username during import sheet 


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

flegare
Regular Contributor III
Regular Contributor III

We actually had this requirement with one of our clients and were able to solve it without pre-processor.

Username generation rule:

flegare_0-1722955691519.png

Importing with basic configuration:

Source file

flegare_1-1722955754505.png

Import config:

flegare_2-1722955796511.png

Aside from that, other import mandatory fields were not checked:

flegare_5-1722956043449.png

Import result:

flegare_3-1722955832044.png

Inserted user.  Username matches the rule defined in Global configuration

flegare_4-1722955933169.png

Key part seems to be on systemUserName generation at import.  I tried the exact same import without the systemUserName generation config checked off and ended up with the same error as OP.

 

 

 

Share logs in text file


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

flegare
Regular Contributor III
Regular Contributor III

Logs attached

Looking like code issue. raise support ticket

"2024-08-06T14:49:18.573+00:00","ecm","services.SaviyntCommonUtilityService","http-nio-8080-exec-31-lxrx5","DEBUG","Error occurred while checking CSV file: Cannot get property 'originalFilename' on null object"


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

flegare
Regular Contributor III
Regular Contributor III

I don't think I need to.  I simply wanted to point out that OP's requirement (generate userName at import time) is achievable, contrary to the answer that was accepted originally.  This worked in our original deployment on 23.10 as well as 24.4.