Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Updated By showing user Name

Tanya10
Tera Contributor

Hi ,
I have done the Service Graph Connector integrations for Tanium and Intune. However, I am observing some unexpected behavior with both scheduled jobs. I updated the Run As account to use the service account, and the Updated By field in the CI List correctly shows the service account. However, in the CMDB 360 Data related list, the Updated By field is displayed as my account/system/admin instead.
Question - Why I'm I seeing 2 different updated by in different tables?

Tanya10_1-1789545324024.png

Tanya10_2-1789545360444.png

 




 

1 REPLY 1

Aljo2
Tera Expert

The first thing I'd verify is whether you're actually looking at the same record in both places.

The CI list is showing the sys_updated_by value from the CI record (cmdb_ci_computer), while the CMDB 360 Data related list may be displaying data from a different underlying record or relationship.

Since your Service Graph Connector job is running as the service account and the CI itself shows the service account in Updated By, that part appears to be working as expected.

To understand why CMDB 360 Data shows admin, I'd recommend:

  • Checking the table behind the CMDB 360 Data related list.
  • Comparing the sys_updated_by value on the CI record versus the related CMDB 360 record.
  • Reviewing the audit/history of the CMDB 360 record to see what process last updated it.
  • Checking whether there are any post-processing, reconciliation, identification, or CMDB health jobs updating that record after the connector import.

In short, if the two views are sourced from different records, it's entirely possible (and expected) for the Updated By values to be different. The key is to identify which table the CMDB 360 related list is actually reading from before drawing conclusions.