- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 11:49 AM
I haven't looked at our import sets for our LDAP in over a year... since someone set us up. There is several errors and it looks like it is only on new users that have come in and it is erroring due to the ObjectGUID field.
The user is in the users table but it won't update his phone number and manager and other attributes. If i click on the date(in the image), I can see the ObjectGUID and then if I go into that users profile and manually paste in the ObjectGUID in the Correlation Field(tartgetfield) and save it and then run the import again, it works perfect and will update the fields.
I am sure I am not making very much sense but how do ObjectGUID's work? I am seeing some that have different ID's(same user) and some that don't have a ID at all in Service-Now. As if when they were created, it wasn't populated...
Hopefully someone can follow my crazy logic. Thanks!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 12:05 PM
ObjectGUID is a global unique identifier to AD. Similar to sys_id in SN. You should be coalese on ObjectGUID and not bring users in without it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 12:05 PM
ObjectGUID is a global unique identifier to AD. Similar to sys_id in SN. You should be coalese on ObjectGUID and not bring users in without it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 12:17 PM
Yes, the objectGUID is the unique identifier in Active Directory, we accidentally coalesced on username for a while but then when women get married or divorced we were having a lot of duplication happening. Then we tried the objectSID, but that changes every once in a while. Then finally we did some real research and found that the objectGUID is the one that doesn't change and is what you should coalesce. I made a guid field on the user record and have it stored there (looks different because of base64 encoding, but is still unique so it doesn't matter)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 12:53 PM
I am coalesing on the ObjectGUID. But I have several users that are in Service-Now that don't have the ObjectGUID in there... so when it tries to update, it errors because it can't find it. How were those created without putting the ObjectGUID in there!?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2016 12:55 PM
Then you turn off coalescence for the first run just to import in all the values (maybe coalesce on username for just this one time) and then once everyone has a guid, then change it back to coalesce there.