LDAP integration is not pulling all the records, missing Cis

Abigail
Tera Expert

a month ago - last edited 4 weeks ago

Hello,
I have a question and maybe you can help me.
I have a CI that was previously populated, but now some information is missing. In the LDAP Browse, I can see that the CI has the required information, like the serial number and userAccountControl. However, when checking the same CI in SN, those fields are empty.

The LDAP filter is not the issue, because I can see the data in LDAP Browse. But for some reason, after running the import, some CIs are missing.

0 Helpfuls
  • 545 Views
1 REPLY 1

Matthew_13
Kilo Sage

3 weeks ago

@Abigail  - 

This usually isn’t an LDAP problem—it’s what happens after the data is pulled in.

If LDAP Browse shows the values but the fields are empty in ServiceNow, it’s almost always a transform or reconciliation issue.

A transform script may be clearing the fields, coalescing might be updating a different CI, or another import is running later and overwriting the data.

I’d start by checking the transform map mappings/scripts and the import order. The data is coming from LDAP; it’s just getting lost on the way in.

Thumbs up if this helps you. Thanks Kindly

0 Helpfuls