Hey Kayla, when you are doing the import have you got “PK:” on the user ID or the user email column?  That should pick it up as the Primary Key to look up the existing users, and do an Update instead of an Add?

Hi Andy, I tried that but it still added them as new users unfortunately. Thanks for your recommendation!

Hi Kayla

Please reference the User Name column with “PK:” - as it’s User Name that is the unique identifier in AdaptiveWork, not the Email address.

That should work.

Hi Limor, unfortunately that didn’t work either it still added a duplicate user.

Which object are you importing against?  That must have something to do with it?  Are you importing a link between existing objects, or the object itself?

Hi Kayla

I apologize for misleading you with the User Name… it is in fact the External ID that should be used to be referenced with PK as the unique identifier:

As dataloader is going through a 2-step process, it indicates for you whether it is about to Update or to Add a record in the system:

A few tip for dataloader:

• only include the fields that you want to necessarily update (+the External ID field in the context of Users) - this will also reduce time for dataloader to perform the action
• always run 1st a load of 1-5 rows to check that all works according to expectations before you move on to a mass update / upload.