Import creating unwanted records

[Ken83]

Hello Community,

        I've been troubleshooting this problem for a bit now and I've come up with nothing so I'll see if anyone here has any suggestions on how to fix this problem. I have an LDAP import that runs once a day and the purpose of this import is to pull groups from AD and insert the corresponding record into SN if it doesn't exist and just update the record if it does exist. The problem that I am having is that it is creating several hundred empty user records. As I mentioned, this import should be inserting group records so I don't know why it's even creating user records. This is my source table...

and my target table...

I am utilizing the "Run Script" functionality and it's been modified a couple of different ways. The first method was using the OOB Script Include LDAPUtils calling on the setManagerField() method and the setManager() function. Only utilizing these 2 methods, it's still creating empty user records. It is worth noting that the only value on these user records is the u_ad_display_name field which should just be the users first and last name. Instead, the value is being inserted as the DN name for the user(which is essentially the AD hierarchy of the location of that users record in AD). But this record shouldn't even exist in the first place.

So the second modification that I made to the transform script, was to run a GlideRecord to the user table, find the user who has a DN that matches the DN of the manager of the group record, get that sys_id and set it as the value for the manager field on the group record. That script is here...

so the end result using this method is the same. I end up with several hundred empty user records with the exception of that u_ad_display_name field which contains the DN for that user.

So any suggestions on what might be causing all of these empty user records to be created?

[Jason Stephens]

Hi Kevin,

Do the records have a "." in them for the user name?   The reason I ask is that I literally ran into this yesterday, and I had to comment out this line:

target.user_name = source.first_name + "." + source.last_name;

in the transform map script for the user import.   I may be way off base, but this was an easy fix for my issue.   Once I commented it out and got the coalesce values straight, it was all good.

Good luck!

Jason

[Ken83 · Accepted solution]

I think I've solved this problem. In my transform map, the u_member field of the import set table was being mapped to the u_member field of the group record. Well, the u_member field of the group record is just a text box, it won't actually do anything. For some reason this was being used to try and add members to the group which it couldn't find any users with a sys_id that matches a CN from AD. So it would create empty records and insert that value as the only value for the user. Removing that field mapping from the transform map seems to have resolved the issue for me.

This is the second time i've found this to be the issue because if you do the same thing for the manager field on a user import that is going to the sys_user table, it may do the same thing. I removed the a similar mapping from my user import and it fixed it for that import as well.

[ayush512]

Hi all,

Sorry for asking the question this late on this thread, what if I have to map the manager field, is there any solution to this instead of omitting the manager mapping??

Please share if you have any other solution.