LDAP: Not all AD Attributes get imported

[Alex125]

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:

[bernyalvarado]

Hi Alex, your import table appears to be empty. Are you successful in importing at least the samaccountname attribute?

Thanks,

Berny

[Alex125]

Benny, for the screen shot only the header. I do get all the records in so that is not the issue.. Just missing the telephoneNumber,mobile,home,Phone,employeeID   attributes (also some others who I do see in the browser but no with import but don't need them so not important)

Thanks.

[Alex125]

Hello,

Clean out the Attribute filter and this what get imported:

Row	Set	State	msDS_SupportedEncryptionTypes	objectClass	instanceType	primaryGroupID	mail	protocolSettings	garbageCollPeriod	userPrincipalName	sAMAccountName	dn	msExchMailboxAuditEnable	msExchDumpsterQuota	msExchArchiveGUID	msExchPoliciesExcluded	uSNChanged	msExchProvisioningFlags	company	name	description	sn	msExchCalendarLoggingQuota	mailNickname	accountExpires	pwdLastSet	showInAddressBook	Target table	Target record	Error

So missing the ones we need (telephoneNumber,mobile,home,Phone,employeeID )

AD filter used normally:(&(objectClass=person)(sn=*)(!(objectClass=computer))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))

Thanks

[conradw]

I'm seeing the same issue an instance, did you ever find a solution?

[Alex125 · Accepted solution]

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.