The mistakes I most often see:
1. the fields are not from the same table occurrence as the portal itself:
When the portal's TO is "j_Stud_cour", the fields should be j_stud_cour::pk_j_Stud_Cour.
2. the fields are overlapping the borders of the portal-row and so showing same in every row:
Make the fields smaller first so they're entirely enclosed by the portal-row border and check, if you get proper values. When they are correct, adjust position and size by selecting and position with arrow key's and set size via inspector.
Another explanation would be that you did a mistake with the Relationship (Table-Occurence) for the portal
Thank you Keywords,
Every time I ask a question on this forum I am very impressed with not only the speed at which people return with an answer but also with helpful suggestions or examples.
I really appreciate your demo.
I'm curious. Why did your portal fail in the first place? What changes did you apply to fix?
While statement 1 may be a 'mistake', it is perfectly legal to have related-related fields in a portal (relationship away from the parent) as grandchildren, for example.
can have the People portal that shows the persons names and the address (of which they may have many)
but it is possible to have selected a field with no relationships and that would be the mistake!
I have #2 as the most often the issue. if the field is not IN the row, it doesn't work. I may need to zoom the layout to 400% to see the problem.