Robust transform map script is not updating the target field
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2024 06:50 AM
Hi Experts ,
SG- SCCM Robust transform map script as given below is not updating the Operating system, on SCCM execution.
Can someone please suggest how to fix it ?
Can someone please suggest on priority , as this is very urgent.
Thank you.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2024 08:18 AM
Is this script operation something you've added as the convention doesn't fit with how IntegrationHub ETL works (you wouldn't perform a GlideRecord.update() within it.
SCCM Graph Connector comes with an 'SCCM OS' import table and transformer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 02:09 PM
I am having the same problem. Using the out of the box SCCM Service Graph robust transform, data source is SG-SCCM Computer Identities. I can walk through the transform using ETL, and see that the operating system should be updated, and if I add the field to a text field, it will get the correct value, but since the OS is a choice field, it isn't updating correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2024 12:43 PM
I just got this working. There are 2 steps that I had to do.
1. Most important, check the reconciliation rules for computers. (Go to CI Class Manager, Open Hierarchy, look at Computer, and find the reconciliation rules). In my case, it was set up incorrectly, and once I added SG-SCCM as priority 1, and selected all the fields, now it will update all of the fields.
2. There are a lot of other posts about the sys_object_source table that will do a better job than I can of explaining how it works. But, to get immediate results, clear out the records from this table for any CIs that you want to update.
This KB article explains what you can do to keep the table a bit smaller and updated: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1198927