Certain Fields on Parent Table Not Available on Child Table

[Nick Peters]

I have a custom, scoped table that extends Task [task]. Most of the fields from Task are available - Assignment group, Assigned to, Subject, Description, etc. - but there are also a handful that are not available. It is a mix of both system- and user-created fields on Task that are not available for me to select on my custom table when configuring/designing the form or when simply looking at the table columns on the table record itself.

Thoughts?

[Brad Tilton]

You should have all of the fields from task available, but not from your extended table by default since the reference is just to task. Is that what you're seeing or is the behavior different?

[Nick Peters]

Sorry, I misspoke in my original post.

When viewing the columns for my extended table, all the fields are available. For the example below, we'll focus on Close notes (a system field) and Completion notes (a user-created field), both of which exist on Task:

When configuring the form layout for this table, those fields are not available even though many other fields from the Task table are:

[Brad Tilton]

Hmm...are those fields marked inactive by chance?

[Nick Peters]

Nope, they're both active. They are not on the form yet either (in case you were wondering since there is a scroll bar in the slushbucket's right side in my screenshot).

The Completion notes field is used on many other tables that extend Task, including a custom, scoped table in a different app scope.