Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
05/09/2024 05:10 AM - edited 05/09/2024 05:11 AM
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.
Solved! Go to Solution.
05/09/2024 06:17 AM
@rohanpandit what is username you expecting may i know ? give some example please?
05/09/2024 07:42 AM
05/09/2024 07:47 AM
Is it like working some and failing for others?
05/09/2024 06:40 AM
Hi @rohanpandit, is user first name and last name empty?
05/09/2024 07:39 AM
05/09/2024 07:43 AM - edited 05/09/2024 07:43 AM
Can you share import job ss once.
05/09/2024 07:50 AM - edited 05/09/2024 07:59 AM
Attaching screenshot. @NM
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.
05/09/2024 09:18 AM
@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.
05/09/2024 07:22 PM
05/10/2024 05:29 AM
@rushikeshvartak via import Job.
05/12/2024 07:04 PM
Username is mandatory attribute and you can't compute username during import sheet
08/06/2024 07:55 AM
We actually had this requirement with one of our clients and were able to solve it without pre-processor.
Username generation rule:
Importing with basic configuration:
Source file
Import config:
Aside from that, other import mandatory fields were not checked:
Import result:
Inserted user. Username matches the rule defined in Global configuration
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.
08/06/2024 08:11 AM
Share logs in text file
08/06/2024 09:12 AM
08/06/2024 09:44 AM
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"
08/06/2024 10:25 AM - edited 08/06/2024 10:25 AM
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.