- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2015 08:52 AM
In our development instance, I rerouted the ldap import to pull from the physicalOfficeDeliveryName and point that to the location field in ServiceNow. It is NOT a field that coelesces; however the objectGUID field is. Everything worked beautifully in development (isn't that how it always works?). I completed the update set and exported it into production. Production didn't pull the new location immediately, so I went into the LDAP import chart and changed the location title (as done originally in dev), and woolah! Production started pulling the correct field for location; however, every user has a duplicate record now. The complete record, with email, phone, userID, and location is not the original record. The original records are missing most everything, but a phone number. I've checked development, and this issue doesn't exist there so I'm at a loss as to how to fix this. Can anyone help!?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2015 05:40 AM
This has been resolved! I was able to run a script to merge any references to the duplicate ID's and then I deleted all the duplicates, re-ran LDAP and everything looks good now. Thanks for the thoughts and input!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2015 05:40 AM
This has been resolved! I was able to run a script to merge any references to the duplicate ID's and then I deleted all the duplicates, re-ran LDAP and everything looks good now. Thanks for the thoughts and input!