I think I need more information than what the screen shots show. Your TOs have names like "Livestock 3" and "Eartag 2"... I don't see Livestock_Mother in there, although I suspect that you mean "Livestock 3".
In any case, I hope I understand enough that this is helpful:
If the context of the layout in your Livestock Entry Form is Livestock 2 (I don't know for sure since there's no indication one way or another), then in order to get the related Eartag Event and Eartag records for the mother would be to create TOs for Eartag Event and Eartag that are linked to the Livestock 3 TO.
In other words, the Eartag Event and Eartag TOs in the graph you attached here are linked to the current Livestock 2 record and therefore do not know who the mother is.
I hope this helps.
Thanks, beverly! Looks like I've got some catching up to do.
Try changing the calculation for LIVESTOCK::mother_eartag_2lines to:
I don't think that that is the case. Livestock_Mother TO is a recursive entity that used a portal record ear tag info., my problem is how to use that portal information. EartagNumber for example was recorded in the Eartagging portal embedded in Livestock and directly in the Livestock entity.
1 of 1 people found this helpful
there may be confusion with what is IN a portal and what is simply a related field (or two) that is not inside a portal, but still valid. Single related fields can be shown on a parent layout, but remember that only the first related record will be shown (as sorted by the relationship on the graph). So IF there is only one related record that is not a bad way to go.
The fields should only be based on the foreign key selected for Mother ID in the parent which would relate to the child in Livestock_Mother (primary key). There appear to still be incorrect context with the latest sample supplied.