Duplicate WID links causing Writeback Issues

Question

Duplicate WID links causing Writeback Issues - Document attached with all data from issue.

Alfred Dean - 73928

Username – ******@la-z-boy.com

Email showing- ******@la-z-boy.com

Workday Writeback error- this means it can’t copy the AD information to WD

Failed to match an entry in the source and target systems User '73928'

 

Error code

DuplicateTargetEntries

Error message

Azure Active Directory entry 83e8aaf5-741e-4930-a8e9-fe8959b0276e matches the Workday entry d40c3c38f207100114f0682e845b0001 based on the WorkerID value { Add:"73928" (Target) }. However, the Azure Active Directory entry 4bc7bea4-508d-42e2-8fb9-a94d365ee85f has already been matched with the Workday entry d40c3c38f207100114f0682e845b0001. Consider deleting the Azure Active Directory entry 83e8aaf5-741e-4930-a8e9-fe8959b0276e, or at least not granting it access to Workday.

 

NOTES:

These are both active Employees I can’t just delete them from Active Directory. This is basically saying that Alfred and Evesvan share the same WorkerID in WD

 

PS C:\WINDOWS\system32> Get-AzureADUser -objectID '83e8aaf5-741e-4930-a8e9-fe8959b0276e'

 

ObjectId                             DisplayName UserPrincipalName  UserType

--------                             ----------- -----------------  --------

83e8aaf5-741e-4930-a8e9-fe8959b0276e Alfred Dean ******@la-z-boy.com Member

PS C:\WINDOWS\system32> Get-AzureADUser -objectID '4bc7bea4-508d-42e2-8fb9-a94d365ee85f '

 

ObjectId                             DisplayName     UserPrincipalName       UserType

--------                             -----------     -----------------       --------

4bc7bea4-508d-42e2-8fb9-a94d365ee85f Elesvan Sanchez ******@la-z-boy.com Member

 

Dezz Jackson - # 73712

Username should be – ******@la-z-boy.com

Username showing: ******@la-z-boy.com

 

When I try to write back to Workday I receive this error

 

Failed to match an entry in the source and target systems User '73712'

 

Error code

DuplicateTargetEntries

Error message

Azure Active Directory entry 9f32b259-c5b4-4264-ab63-327a6ba51764 matches the Workday entry 8e525720a1081000be5b22198d4e0000 based on the WorkerID value { Add:"73712" (Target) }. However, the Azure Active Directory entry 6ef17e75-16eb-4b25-bb1a-f54a281b4262 has already been matched with the Workday entry 8e525720a1081000be5b22198d4e0000. Consider deleting the Azure Active Directory entry 9f32b259-c5b4-4264-ab63-327a6ba51764, or at least not granting it access to Workday

 

NOTES:

PS C:\WINDOWS\system32> Get-AzureADUser -objectID '9f32b259-c5b4-4264-ab63-327a6ba51764'

 

ObjectId                             DisplayName  UserPrincipalName     UserType

--------                             -----------  -----------------     --------

9f32b259-c5b4-4264-ab63-327a6ba51764 Dezz Jackson ******@la-z-boy.com Member

 

PS C:\WINDOWS\system32> Get-AzureADUser -objectID '6ef17e75-16eb-4b25-bb1a-f54a281b4262'

 

ObjectId                             DisplayName    UserPrincipalName     UserType

--------                             -----------    -----------------     --------

6ef17e75-16eb-4b25-bb1a-f54a281b4262 Ariana Robledo ******@la-z-boy.com Member

 

These are both active Employees I can’t just delete them from Active Directory. This is basically saying that Dezz and Ariana share the same WorkerID in WD

 

 

It looks like somewhere. It is getting connected to this person, but it doesn’t appear to be on the AD side ☹

 

 

 

Answer 1

I had this same issue today. It was caused by the incorrect employeeID being assigned to a user. This caused 2 different Workday users to have the same email address and when the Workday Writeback sync ran, Workday associated the Azure user with the wrong Workday account.

We corrected and compared all attributes in AD, Azure, and Workday, but on user1 we were still getting WorkdayInvalidAnchor - Validation error occurred. User Name already taken, please choose another one

and on user2 we were getting:

Failed to match an entry in the source and target systems

DuplicateTargetEntries

Azure Active Directory entry [redacted] matches the Workday entry [redacted] based on the WorkerID value { Add:"[redacted]" (Target) }. However, the Azure Active Directory entry [redacted] has already been matched with the Workday entry [redacted]. Consider deleting the Azure Active Directory entry [redacted], or at least not granting it access to Workday.

This was resolved by changing the Integration IDs > External ID in Workday for the user with the WorkdayInvalidAnchor error to a new unique value. This has to be done by a Workday admin on the Workday site and does not appear to be updatable on the Azure config.

I was able to provision on demand user1 and then user2 without error.