3 Replies Latest reply on Jul 23, 2013 6:44 PM by keithr

    Linking users to objects by "unique" login id instead of display name

    keithr Specialist

      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.

        • 1. Re: Linking users to objects by "unique" login id instead of display name
          Stu McNeill Employee

          Hi Keith,

           

          In your data import mapping if you map to the relationship this will rely on the IsName attribute of the object (Title in the case of User).  However if you expand the relationship and map to an attribute, then right-click on the relationship and set the Target Key attribute to the same then this will allow you to import based on anything.  This is also the best practice for importing into relationships.

           

          Thanks

          Stu

          • 2. Re: Linking users to objects by "unique" login id instead of display name
            keithr Specialist

            Hi Stu,

             

            I had tried this method of mapping directly to the user.name attribute which holds the network login.  Although this worked if I just one user is mapped, if I map two users, following save, both mappings updated to the same mapping.

             

            For example, if I create a mapping as follows: 

            • Account code > AccountCode
            • User1.networkLogin > User1.Name
            • User2.networkLogin > User2.name

            Both users have the "name" attribute set as the target key, "title" is mapped to "display name", and the target key on the top object is "Account Code" (this is the object that I am importing into)

             

            Following save, the mappings revert as follows:

            • Account code > AccountCode
            • User1.networkLogin > User1.Name
            • User2.networkLogin > User1.name

            The second user reverts to the same mapping as the first one.

            I have logged this with support but if you have come accross this before, please let me know if you managed to resolve it.

            • 3. Re: Linking users to objects by "unique" login id instead of display name
              keithr Specialist

              Hey Stu,

               

              I was using the same column in the source file to map the display name (Title).  Once I seperated the columns for the display name, the issue mentioned in my second post went away.

               

              Thanks for your help!

               

              Keith

              1 of 1 people found this helpful