Extended Table misunderstood

[connortj]

I'm having a problem with extending a table.   I have a base table (custom) that I have declared as extendable. This base table contains legacy data with existing records.   I created another table(child) that extends the base table to create NEW records (not using ALL the base table fields).   This seemed to work as I thought.   I was able to add records to the base table using the extended table just fine until I went to the base table and tried to open up a record create from the child... It showed only the fields for the child table and instead of showing the fields for base table in the UI, it only showed the child table UI. (Class is different).   What I was expecting was the child table record, that was now in the base table to display like the rest of the already existing records.   Am I missing something in my understanding of extended tables or did I just assume too much?   Thanks for any guidance!

[darius_koohmare]

You are mostly correct.

When you extend a table, the child table inherits the columns (fields) from the parent for use. The child records are living on the child table, and are subject to the forms and views that where created for that child table.

When you look at a list view for the parent table, it will include all child records.

When you click the child record, it is expected to be rendered   in the form and view of that child table, as that is still where it resides.

It will not render with the form of the parent table.

Example: Server is a child of Computer. When you look at the Computer list, it includes Servers. But when you open the Server record, it displays the Server form, which is intended.

[darius_koohmare]

If you want it to show the same form of the parent table when clicked from the parent list, I advise using views.

You could define a view to the list, and define the same view for the child table that has the form fields on it you would like.