how to populate manager field from AD, we have tried everything as per the Wiki article, but still no luck, we are using Sam AccountName as query

manpreet · ‎03-10-2016

jhauptmann · ‎03-11-2016

I just recently had the same issue and a colleague suggested I check the field lengths in the import set table. What worked was increasing the field length for "manager" to 250 from the default which was 40.

Under Tables look at the User(imp_user) table and see what the field length is. We also bumped up source, dn and bumped memberOf way up (2000) as that value can be quite long.

This may not work for you since you've been using SN for a while but might be worth checking.

Regards,

John

View solution in original post

TrevorK · ‎03-10-2016

This is what we have been using since the Aspen release without problem:

The Script field you see above is the Script field right on the Transform Map itself (not an onBefore, onAfter, etc.).

We also have this in an onComplete:

And this is an onStart, which I assume is the most critical piece to it all since it loads LDAPUtils to be used in the other pieces.

One catch with all of this is that you DO NOT map the Manager field in your Field Map.

Is the above what you have and still not working? I am unsure how the Wiki documents it - we set this up 4-5 years ago and it has been working perfect since.

jstifflear · ‎03-10-2016

Hello,

Your onStart and onComplete scripts look good. I would check two things:

First, verify that your Field mapping for your user import does not have a mapping for manager as this is not needed here.

Then you need to verify the manager attribute is in your LDAP server attributes. Drill into your LDAP server record and switch to Advanced View. Confirm that manager is in the list, if not you need to add it (comma separated). This is the list of attributes that ServiceNow will retrieve from LDAP, regardless of your mapped fields in your transform.

Once you have this completed, perform an LDAP sync and check to see if the manager field is getting updated.

I hope this helps you resolve your issue.

Jim

jstifflear · ‎03-11-2016

Hello Manpreet Chadha,

In my comments above I meant to say that the onStart and onComplete scripts posted by Trevor Kuebler look good. Verify your Table Transform Maps are correct as well as the transform scripts and make sure that manager is listed in the LDAP Server Attributes.

Jim

Vladi1 · ‎03-11-2016

Do you have error on the LDAP or transform map?

When I worked on LDAP integration I used transform maps. If I am correct you have to add manager field to the attribute list and to map it to your manager field in transform map and ran it manually.

Vlady