- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2020 11:50 AM
I need to know what specifically triggers the [sys_udpated_on] field to get updated (I know EVERY type of change/modification in ServiceNow (SN) does not trigger it to get updated). Long story short: We have an external reporting system that we use for advanced reporting/queries. The updates to that external reporting system are done on an incremental basis. The incremental updates from (SN) are based on the [sys_updated_on] field. Therefore, I need to know what types of updates will/will not make it into our external reporting system.
Solved! Go to Solution.
- Labels:
-
Reporting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2020 07:06 AM
Hi,
sys_updated_on column on every table is defined by default in the Database of ServiceNow.
- These gets changed whenever there is a manual change in the record.
- Any business rule/script include/workflow/server side script updating the records will update this value.
- This doesn't get updated when there there is this code: autoSysFields(false); in the server side script.
- When you have a code which update sys_updated_on field, this doesn't get updated.
- This will not change sys_updated_on when you save a form, update a record through script but there are no changes in the record.
Check out these community articles for reference:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2020 11:28 PM
Hi Dirk,
As long as this script gets executed in any session through the ways you mentioned, it will skip updates on sys_updated_on field.
There is no validity for this function, exception that the session should not get expired.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2022 02:07 AM
Does changing in relation table, such as cmdb_rel_ci, changes sys_updated_on in attached cmdb_ci records?
If yes, is the propagation continue to all related cmdb_rel_ci and cmdb_ci records?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2020 06:52 AM
Thanks all. We have a few (small percentage) of records where, we know the record changed, but the sys_updated_on field did not get updated. We don't know why yet - thus the reason for my question. I think your responses, Gowrisankar/Dirk, may probably hold the key.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi Korynn, did you in the end find the reason behind the small percentage of records where the sys_updated_on didn't update? How reliable is the export now? We are planning a similar incremental export and I want to verify that we won't be missing any updates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2020 09:18 AM
And thank you to Debopriya as well 😉
