and more in a single search tool across platforms. Read the announcement here. |
01/07/2024 11:40 PM
Hi,
I've noticed that after upgrading to releases v23.9 and v23.10 from either 5.5 or v23.5 our Sav4Sav user import jobs have started to behave differently. If a user import job uses a query that updates the same user more than one time, then this will wipe out all user attributes that were not updated by the job. This has resulted in some production issues because also the user attribute used as the reconciliation key might be emptied and in this case the next import from HR source has created a duplicate user, so the issue has forced us to do some data cleanup in customer environments. The issue has been noticed in three different customer's environments with multiple jobs.
Obviously we can design our queries so that the same user is never updated more than one time and the queries have been changed to avoid this from happening. However I'm wondering if this is expected behaviour fro Saviynt or is it a bug that will be fixed in an upcoming release.
The issue happens with both DB connector and REST connector based Sav4Sav user import jobs.
best regards,
Sampo
Solved! Go to Solution.
01/08/2024 07:01 PM
You should raise support ticket
01/09/2024 11:14 PM
Hi @Sampo
This is a known issue and fixed in 23.12. Please refer to the release notes for details.
Release Notes v23.12 (saviyntcloud.com)
CONN-13841 | While importing users with multiple entries in the API response, the REST connector clears attribute values that are not mapped in the colsToPropsMap attribute of the ImportUserJSON parameter for such users |
Regards,
Dhruv Sharma
01/09/2024 11:27 PM
Thanks Dhruv Sharma, this is good to know!