Click HERE to see how Saviynt Intelligence is transforming the industry. |
07/03/2024 06:52 AM
I have a user import job with the reconciliation field set to secondaryEmail and have staged a test user with secondaryEmail populated with the value coming from the identity source. The problem is that the import job completes successfully but does not update the user record. The secondary email value is coming through from the Auth source as you can see in the mappings below:
"RESPONSEDATAPATH3": "Body.StreamReportResponse.ReportStream.DECODEBASE64.data.row", "USERMAPPING3":"FIRSTNAME:value(0),PREFEREDFIRSTNAME:value(1),LASTNAME:value(2),EMAIL:value(3),TITLE:value(4),DEPARTMENTNAME:value(5),LOCATION:value(10),CITY:value(7),STATE:value(8),CUSTOMPROPERTY2:value(9),CUSTOMPROPERTY3:value(6),CUSTOMPROPERTY4:value(11),SECONDARYEMAIL:value(12),EMPLOYEEID:value(13),USERNAME:value(13),STARTDATE:value(14),MANAGER:value(15),TERMDATE:value(16),CUSTOMPROPERTY5:value(17)",
"TEMPMAPPING3": [
"EMPLOYEETYPE='EMPLOYEE' WHERE EMPLOYEETYPE IS NULL",
"STATUSKEY='1' Where CUSTOMPROPERTY5 in ('Active')",
"STATUSKEY='0' Where CUSTOMPROPERTY5 in ('Terminated') "
]
Any idea why the linking is not working?
07/03/2024 10:26 AM
@jralexander137 may i know use case? can you try reconciliation field as 'username' or systemusername
07/03/2024 10:30 AM
Prehire user record will be created in saviynt with personalEmail populated in username and secondaryEmail via createUser API. Then when user is hired, they show in auth source with full user record of attribute. User import job configured for UPDATE only should then reconcile 'new' full user record in auth source using personalEmail as reconciliation field.