How to check for updates to tables that are not recorded in the Update Set

[Ohki_Yamamoto]

ServiceNow recognizes that there are two types of TBLs: TBLs whose updates are recorded in the Update Set for each TBL, and TBLs whose updates are not recorded in the Update Set.

Whether or not an update is recorded in the Update Set can be determined by whether or not there is an UpdateSynch=true record in the Attribute of the sys_dictionary table. (If there is a record with UpdateSynch=true, it is recorded in the Update Set.)

Currently, we would like to mechanically check if a record has not been updated for a TBL that is not recorded in the update set. Is there such a function in ServiceNow's OOTB feature?

It is possible to implement a script to identify the target TBL and check for record updates, but we would like to see if there is a simpler way to do this.

[Arun_S1]

@Ohki_Yamamoto Your requirement is not clear, please clarify on what you would like to check.

Please mark the appropriate response as correct answer and helpful.

Thanks!!

[Ohki_Yamamoto]

@Arun_S1 

I would like to check if there is a mechanism to mechanically detect records that have been updated in the TBL that are not recorded in the Update Set.

Right now, my project is experiencing release leaks of materials that are not recorded in the Update Set. (For example, if I needed to release a record in kb_knowledge, I need to release kb_version along with it, but I have not been able to release kb_version.)

Therefore, we would like to know if there is a way to check whether or not a record has been updated for a TBL that is not recorded in the Update Set.

The kb_version, for example, is not recorded in the Update Set. Therefore, we need to know in advance that the record in the TBL named kb_version is updated and that we need to release it together with kb_knowledge, otherwise we will not be able to release it.

Even if we do not know the specifications of each TBL in ServiceNow as described above, we would like to check if there are any records that should be released for TBLs that are not recorded in the Update Set or if there is any OOTB functionality.

[Arun_S1]

@Ohki_Yamamoto My understanding is that you are migrating data using an update set and that data is not getting migrated properly as the dependent tables are not being captured in the updated set.

For example you create a new category and a KB article for the new category, since update_synch is enable KB article is captured in the update set but the category is missing.

So you would like to know what are the dependent tables for a respective table that is captured in the update set and are there any new records added to those dependent table which has to be migrated as an XML.

Unfortunately there is no OOTB functionality that can give you a report of the data that is added manually and needs to be migrated.

Please mark the appropriate response as correct answer and helpful.

Thanks!!

[Ohki_Yamamoto]

@Arun_S1 
Thank you very much!!

I am think that when I create a new category and a new KB article for a new category, neither the KB article nor the category is captured in the Update Set because neither kb_category/kb_knowledge has an update_synch record. (It works that way in PDI.)

kb_knowledge recognize that update_synch is not true, but is the perception different?

I understand that records not captured in the update set can only be released manually, and that there is no functionality available in OOTB.

Please advise for reference.
Mr.Arun_S1, when releasing records that are not captured in the update set, what controls/checks are in place to ensure that there are no omissions in the release?
If you have an effective method, I would appreciate it if you could let me know.