How to configure a custom table so that every UPDATE/INSERT/DELETE in that table is tracked in an Update Set? Warning about the use of the "Track in Update Sets" UI Action of the [sys_db_object] table.Description<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } table tr td { padding: 15px; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } hr{ border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc; } ul { list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> This Knowledge Article explains how to configure a custom table so that every UPDATE/INSERT/DELETE in that table is tracked in an Update Set. There is an OOB Dictionary Attribute named "update_synch" by which we could get this but adding this Attribute to a Dictionary record is NOT supported. Refer to the Customizations tracked by update sets documentation page. Notice the following warning: ResolutionIf the custom table has not been created yet, make it extend [sys_metadata]. If the custom table exists already, you can use the OOB UI Action on [sys_db_object] named "Track in Update Sets". This will re-parent the table to [sys_metadata] but this should be used with caution. Although the change of the [sys_db_object] record will be captured in an Update Set, the reparenting process will not be carried out when promoting the Update Set to another instance. This will result in orphan data and has been reported in PRB136464. This means that the table on the target instance will need to be reparented by ServiceNow. Make sure to note the following limitations: We do NOT support adding the Attribute "update_synch=true" to the tables directly.2. We only support extending [sys_metadata], in limited circumstances (see below).3. We will not re-parent tables the customer didn't author.4. We will not re-parent tables that already have a parent.5. We will not re-parent a table you don't have permission to delete.6. You can create new tables that extend [sys_metadata] directly without using this UI action. That is strongly preferred to re-parenting. Example of a table configuration captured in an Update Set (creation a new column): Example of a data creation/change captured in an Update Set. Notice that the Type = Name of the custom table. Additional InformationWe have a known issue about the use of the "Track in Update Sets"" UI Action which can trigger the following error: "Invalid 'Table' selected on the Form Section record. The 'rep$x_autuk_snc_test_form_issue' table is in application 'Global', but the current application is 'snc_test'." See KB0725802 for details.