How to start tracking a custom table?

[peterraeves]

Long time ago a custom table was created, and it does not look like it is being tracked as changes to not appear in the update set. I read that you should extend the table from the Application File table at creation for this to work (Track an application table in Update Sets ). Is there a way to start tracking the custom table, even after it was created?

[Chuck Tomasi]

There it is! Yes, things just keep getting easier and I don't always have the simplest approach. Thanks for sharing Peter!

[JefDeCoster]

Only works in NON-Extended tables

[JefDeCoster]

Hi All,

Mentioned UI Action will only work for NON-Extended Tables.

Eg. if you are in a table extending Data Lookup Matcher Rules[dl_matcher] the ui action won't show up.

Which is expected behaviour, because the ui action would reset extenting table to "Application File" 

As explained in the UI Action itself:

Make a table update synch by reparenting a non-extending table to Application File ( sys_metadata ) - this is the mechanism to set a customer table to update_synch

If you want to Track an already extended table, you can by adding the attribute update_synch=true, as refrenced here : https://docs.servicenow.com/bundle/london-application-development/page/build/system-update-sets/refe...

KR

Jef