Importing Assets via CSV mistakingly creates Requesters?
In ServiceDesk v7 7001
We have imported our user base via Active Directory, however when we attempt to import Assets from a CSV file, and we define a column for the User associated to the Asset, a new Requester is setup.
So for instance we have a user called Geoff, whose details have been pulled across from Active Directory. Now when I import my Assets from a CSV file, I have a record for Geoff's laptop and a column titled "Allocated To". Upon completion of the import, I can go to my list of requesters and not only do I have the correct "Geoff" which came across from Active Directory but I also have a double up account, named "Geoff" as well except it has no other details.
How do we stop this doubling up?
We have imported our user base via Active Directory, however when we attempt to import Assets from a CSV file, and we define a column for the User associated to the Asset, a new Requester is setup.
So for instance we have a user called Geoff, whose details have been pulled across from Active Directory. Now when I import my Assets from a CSV file, I have a record for Geoff's laptop and a column titled "Allocated To". Upon completion of the import, I can go to my list of requesters and not only do I have the correct "Geoff" which came across from Active Directory but I also have a double up account, named "Geoff" as well except it has no other details.
How do we stop this doubling up?