Unable to pull in employeeID attribute from AD via LDAP

[Basim4]

Hi SN Community,

I am attempting to pull in the employeeID attribute from an AD user object to its corresponding ServiceNow user record but without any joy.  I have specified the employeeID attribute in the 'Attributes' field on the LDAP Server form, and also have tried clearing all the attributes from this field but when I browse the LDAP OU Definition the employeeID attribute does not display while all other attributes do.  (The employeeID attribute is populated on the AD user object records that I am browsing).  I have also cleared filtering to ensure when I browse the AD OU structure, user objects that have this attribute populated are returned.

Has anyone managed to pull across the empolyeeID attribute from a AD user object to its corresponding user record in ServiceNow?

Any suggestions would be most welcome!

Thanks,

Bas

[SanjivMeher]

Did you check the ldap import set...

After adding the attribute to the LDAP Server and running the integration, a new field should have been created. It mayn't appear on the list view. From personalize view, you can add it to the list view.

[Basim4]

Hi Sanjiv, Unfortunately not - it didn't appear. I even tried creating the employeeid field on the import set table and used mapping assist to match the source and target field. Any further ideas? Thanks, Bas

[SanjivMeher]

Are you sure empolyeeID is the correct AD attribute. when you manually created te import set field, the field name soud be u_employeeid. Is that how it is?

[Basim4]

Hi Sanjiv Quite certain (near enough 100%) that employeeID is the correct attribute and when I manually created the import set field it is u_employeeid. It's really odd that all other attributes come across fine - just not employeeID for some bizarre reason.