- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 09:25 PM
Good afternoon
We have bunch of assignment groups in AD ( Active directory) and we set LDAP sync.
Whenever I rename an assignment group.. in servicenow now another record/group is created, and the old group still exists. I check the transform maps.. all source and target fiels seems to be set properly..only sAmmaccount is coalesce
Any advise?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 10:36 PM
Hello @samirmeroua ,
I would recommend always coalesce on a stable, system-generated identifier (like objectGUID) rather than a human-readable field (sAMAccountName, cn), because those can and do change. This ensures your sync process is idempotent and prevents duplicate records.
Refer this :
Advice regarding LDAP import coalesce (ObjectGUID)
If my response helped mark as helpful and accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 09:54 PM
Hi @samirmeroua
Check this post : https://www.servicenow.com/community/developer-forum/groups-syncing-with-active-directory/m-p/264537...
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2026 10:36 PM
Hello @samirmeroua ,
I would recommend always coalesce on a stable, system-generated identifier (like objectGUID) rather than a human-readable field (sAMAccountName, cn), because those can and do change. This ensures your sync process is idempotent and prevents duplicate records.
Refer this :
Advice regarding LDAP import coalesce (ObjectGUID)
If my response helped mark as helpful and accept the solution.
