Notifications

41 views

Overview

The skip_sync field not only exists on assets but also on cmdb table. It is the flag indicating whether synchronization between Asset and CMDB can be skipped. See the following document: 

https://docs.servicenow.com/bundle/london-servicenow-platform/page/product/configuration-management/reference/cmdb-table-property-descriptions.html 

There are OOTB script includes and business rules that may invoke according functions and change the value of skip_sync: 

AssetAndCISynchronizer 
https://<InstanceName>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=9ec37b411b012000e49bfbcd2c071380 

Update Asset fields on change 
https://<InstanceName>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=31e93aaf1b3210002502fbcd2c0713d8 

Update CI fields on change 
https://<InstanceName>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=4d15855c1b0310002502fbcd2c071399 


skip_sync flag is used to prevent recursion within the same cycle of business rules and will be reset in next cycle during Asset-CI synchronization. The skip_sync flag is set to false by default.

As the two business rules above would be triggered twice during an Asset-CI synchronization. The skip_sync flag would be set to false again after the synchronization. In case the skip_sync flag was set to true for some reason, an update on the Asset/CI should help set the flag back to false.

Article Information

Last Updated:2019-03-13 00:17:46
Published:2019-03-13