Custom extended table displaying in parent table module

[gjz]

I have not run into this problem before and don't know how to solve it.

I have created a custom application through Studio.  The custom app has two custom tables in it, the parent table that is extended from the Task table and a child table extended from the parent table.  I see the child records in their module as expected, but I also see the same child records in the parent's module, which I don't expect.  Does anyone know why this is happening?

Here is a screen shot - RMAT is a child record from the child table extended from the parent RMA table and shouldn't be in the list.

[Mark Roethof]

I do wonder why your RMAT is extended from RMA and not extended from Task? For example Incident is extended from Task, Incident Task is NOT extended from Incident, though also from Task. Same for Problem and Problem Task, Change Request and Change Task.

Might this be a small design error you made in extending the wrong table?

[gjz]

It was originally, but I changed it because of the custom fields.  Because of the flow and processes, I found it a pain to create the same custom fields in the child table and pass information back and forth between the two.

[Mark Roethof]

Okay so its by your own choice that this behavior occurs. In that case see my other comment, update the Module and its condition. Nothing more. Few seconds work to add the class to the condition.

[Mark Roethof]

Just out of curiousity, you mentioned havings fields on the RMATask which are also on the Parent, which is one of the reasons why extending the custom parent RMA table and not the Task table. Those fields, do they contain different values as the Parent RMA or do will they have the same values? The last I see often in designs, though in that case if that's really necessary you could also add the dotwalked fields instead from the Parent RMA.