LDAP: Not all AD Attributes get imported

Alex125 · ‎08-12-2015

We like to import data from AD to our User table. And the next Attributes we like to import from AD: sAMAccountName,mail,telephoneNumber,mobile,home,Phone,employeeID

But the only ones we get of that list is sAMAccountName,mail. The rest of that list is not get imported but when we do browsing within ServiceNow I can see them. So there are available from AD/MID server

Off course try it with a empty table and a new table table and switched off the filter but the same issue..

Any ideas? We are now on Eureka version.

Browsing we see the AD Attributes so connection is ok and can get it from AD

But after import:

Alex125 · ‎10-28-2015

Yes, the issue is that the import function sample only the first 20 records what it gets in to build the import table. As we import AD from the root the first 20 records had not all the data in them (also get the wrong length of fields etc.) So two options to resolve this.

- Point to OU that has all the data in the first 20 records

- Create those fields manual in the import table. Be sure you use the correct names

Also you need to check you fields format as that is not always correct. Like the source and DN field is only 40 characters long and that should be 255 (not that you ever use that but that is the standard for AD).

And never Clean the whole table as you loose the structure then, so you need to do all the work again..

Hope that helps you.

View solution in original post

conradw · ‎10-28-2015

Great thanks for the help and info Alex, really appreciate it.

Conrad

Alex125 · ‎10-28-2015

A remark on this. When you do this: - Point to OU that has all the data in the first 20 records

You get then the correct structure of you import table so then you can point back to the root of AD (that how I did)

And have a schedule import from the AD root what works fine then (as long you don't clean out the structure of you import table).

conradw · ‎10-28-2015

Thanks will do.

Nickels · ‎11-10-2015

Thank you for this, I was running into the same issue and this resolved it for me as well.

-Chris

akzm · ‎08-28-2015

Hi Alex,

Do you have the columns for these fields in the import table? Look for columns like u_mobile, u_home, etc? You're not supposed to create any of these columns yourself, import process does; so I want to check if it did.

Also, are you importing via MID server?

Thanks.

Azfar