You may want to mark the reference column in the child table as “ISPartof” for the related records from the child table to appear in the parent form. But please do read the restriction that is associated when you select the “Is a Part of” setting.
The restriction is when a parent record is deleted the “IsPartof” child records are also deleted when you enable this setting.
Since it is not always correct to set it (depends on your use case and your case seems to fit this one), you can keep the workaround in your tool box. (It seems you are having issues with both of them…)
I think use case is when orphan children records are not practically required and parent /children tables functionality is closely integrated. For example an Order( parent table) and its Order details ( child table). In majority of cases , once an order is deleted, order details make no sense. A task is deleted , then the related activities can also be deleted and so on.
Hi @Pejme and @TeeSee1 , The configuration is explained in detail in the article below under the topic "Express ownership between table"
There must be some setting or something in one of my tables because I was able to implement the child table in the parent table form for two other tables, but I can’t get it to work for these two tables