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

User Import /Rehire not working

Samiksha
New Contributor
New Contributor

 After upgrade to 24.4, when we rehire a user from the users' tab through csv file we are seeing no records were updated or inserted and in error we could see below - 

ERROR services.ImportSAvDataUserService - End date is lesser than the Start date specified in the csv.

Please note by our design the end date should be less than the start date in case of rehire users. We are setting term date to end date for all terminated users and In case of rehires this field is being used to trigger user update rules for rehires (enable account if account already exists within 30 days or create new account)

This issue is occurring only in our test env, whereas in DEV (same version 24.4) its working and triggering user update rule after import.

Is there any reason why it works in one env and not in the other?

Any workaround available to handle such situation?

 

4 REPLIES 4

NM
Valued Contributor II
Valued Contributor II

Hi @Samiksha , practically if a user is rehired, end date should change to the new one which should be greater than startdate.

Samiksha
New Contributor
New Contributor

In our design, when a user is terminated we set the "term date" to "end date" .

Upon rehire thru HR feed file user will have a new start date now, term date will become blanck. 

Now the end date which was set earlier will be used to calculate whether the user is retired within 30 or after 30 days and provisioning rules to enable or create new account will be triggered.

This was working well untill 23.10, but in the upgraded env import of such users having end date lesser than start date is failed.

Please validate sub version of 24.4 in both environments 


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

Samiksha
New Contributor
New Contributor

Yes there was a subversion difference between both the environments. Issue is resolved after applying subversionfix