Moving to a new User source

[ACrosthwaite]

We have in the past been asked to move the connection of our pre-production Workday RAAS connection from one source to another. When we have done this before despite the data being almost an exact match when we have done this we have ended up with duplicate users being created.

We would have expected that given we used the employeeID attribute coming from the workday sandbox environment that moving to a new workday sandbox environment which has the same employeeIDs that these should just reconcile with existing users and not create new ones as we've seen in the past.

[AmitM]

@ACrosthwaite , is workday worker ID , username in Saviynt? 

We have different workday environments integrated in preprod and different database connector as well , and using username as recon field in Job (Diff envs Workday Job) and in connection for DB.

We have seen people coming from different sources with no duplicates.

Thanks,

Amit

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.

[ACrosthwaite]

@AmitM not exactly below is an extract from the JSON we have configured in the user import mapping as you can see we are using Employee_ID as username.

{
"ImportType": "RAAS",
"ResponsePath": "wd:Report_Data.wd:Report_Entry",
"ImportMapping": {
"USERNAME": "wd:Employee_ID~#~string",
"FIRSTNAME": "wd:Preferred_First_Name~#~string",
"LASTNAME": "wd:Preferred_Last_Name~#~string",
"DISPLAYNAME": "wd:Preferred_Full_Name~#~string",
"LOCATION": "wd:Location~#~string",
"TITLE": "wd:Position_Title~#~string",
"EMPLOYEEID": "wd:Employee_ID~#~string",
"PHONENUMBER": "wd:Primary_Work_Phone~#~string",

...

[AmitM]

can you share your user import Job details?

Thanks,

Amit

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.