Am working at a university where there is a requirement to create a relationship between a "Financial Delegate" user and an "account code" reference list. The requirement includes the ability to import updates to the account codes and change the financial delegates accordingly.
Typically this can be achieved by associating the user object with the required list, in this case the account code. Then importing into that list.
However, the issue I have is that the financial delegate (end user) might also have a student account with the same display name. i.e. "keith riordan" is my display name for both of my end user "employee" and "Student" account.
Although LANDesk allows 2 different users with duplicate display names to exist, it also creates user relationships based on the "Display Name" and not the network login. i.e. my account code import must use the (non unique) "display name" instead of the (unique) network login which is the unique identifier for account that I want to associate.
Therefore, the import is going to associated the first display name it finds with the account code. Since it is not using network login (and since it is possible to have 2 users with the same display name), it is possible that an incorrect association could be made.
If anyone has found a succesful way of importing users against an object via the network login (Name) attribute instead of Display name (title), would be great to know how.