How to stop SGC updatign the 'assigned to' field on insert or subsequent updates.

[Carl Fransen1]

Hi Team,

We are using both SC-Intune and SG-SCCM, along with discovery.

I do not want any of the above to set the 'assigned to' value on insert or update.  How do I go about this?

I've set reconciliation rules for all 3 sources where only update if 'assigned_to' value is NULL.  Plus I've set Data Refresh rules for each where the stale is 5000 days - to avoid other sources from updating.

I've also set the system property: 'glide.wmi.assigned_to_always_overwrite' to false.

Any help is appreciated!

[Ashish37]

Hi @Carl Fransen1 ,

I if you do not want SC-Intune and SG-SCCM, and discovery to update assigned_to then remove this field from all the 3 reconciliation rules.

Thanks,

Ashish

[Carl Fransen1]

Hi Ashish,

If I remove the rules for 'assigned to' then it will behave like OOB where it updates it anyway?

Currently I have reconciliation rules that should only update if the field is 'blank' but it still 'flip flops' between values from different sources every time the sync occurs.  Not sure why these reconciliation rules aren't working correctly. 

However - I don't want the value updated at all when first created, which I'm not sure the reconciliation rules work on as these seem to only be for after the CI is created? 

[Nitin Panchal]

If anyone is still looking for the same on how to disable graph connector field update , here is KB article published by ServiceNow
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0958725

[Carl Fransen1 · Accepted solution]

What worked for me in the end was to set the source to one we weren't using (in our case LANDesk) and this meant that our other sources didn't update as LANDesk was only given the rights to be the source of truth.