Prevent records from a scoped table being captured in Application

[The SN Nerd]

I have a table in a scoped application that extends 'Scheduled Script'.

For some reason, all record create/updates for that table are being captured in the Update Set (not talking about configuration, but record creation).

This is especially strange because the Scheduled Script table is normally not captured in Update Sets and I did not set this table up to be captured in Update Sets,

The new/updated records for this table are not being captured in any Update Sets, yet they continue to be added as an Application File with every record update.

That being said, the 'track in Update Sets' UI Action is not available.

No parent tables in the hierarchy are set to capture in Update Sets.

I have also added the 'update_sync=false' attribute.

Is there any way to stop this from happening?

I think I need to stop this table from extending sys_metadata but unsure how to do this and how this happened in the first place.

[Pradeep Sharma]

Hi Paul,

You are correct. You have to clear table extend from sys_metadata. Please refer below thread where I have answered.

Remove a Custom Table Data from Update Sets (unextend Application File (sys_metadata))?

[The SN Nerd]

I'm not sure that will work in my example.

The 'super_class' field on my table is "Scheduled Script Execution", and it would completely break the functionality if this was removed.

[The SN Nerd]

I've found the base table 'Scheduled Job' extends Application File.

It is outside of my application scope, so there is essentially nothing I can do about it.

I'm just really surprised this table extends Application File OOB.