Gathering data and displaying as a list for a common relationship.

I’m attempting to gather and display data from several records CONTACTS on a common record SCHOOLS.

Example, we have a SCHOOL, that is related to CONTACTS person A, B, and C. I want to look at a field in school “Paid” and see when these people “Paid”

Right now what I’m doing is using a work flow, When person A has a field “paid date” = to today, a workflow copies their name to a Hidden field in SCHOOLS.
When this happens another field takes the hiddenfield value in schools {p0} and the data for what is existing in the Paid field {p1} and reinserts this into the paid field {p0} {p1}.

What I end up with is this PERSON A 2/1/2018, PERSON B 7/1/2018, PERSON C 8/9/2018. I would like to do this in fewer steps and format it more like a list.

PERSON A 2/1/2018
PERSON B 7/1/2018
PERSON C 8/9/2018

Not matter what operator I use in the calculated filed formula box ( {p0} “\n” {p1} or {p0} PHP_EOL {p1}) it will ignore the formatting because of the way it saves and I end up with one long string.

Thanks for any tips or pointing me in the correct direction.

Maybe the way you’re designing it isn’t the best… I don’t think you should be copying data around just in order to show it in a different place.

You should be able to organize your modules and data so that everything you want would show in Detail views, with the appropriate subpanels.

For example, it looks like your School record’s detail view could have a subpanel showing the related Contacts records, and a custom column showing when they payed.

That is correct, what I’m aiming for is getting the information to print on a PDF generated by the school module. Do you have any information on how to reference another module when generating a pdf?

Or better yet can I append data in a field using a logic hook or some other method?

Have a look at the Reports module, there it is easy to include sub-modules under modules in grouped lists.

I would always avoid copying data to other fields, that always generates problems with data consistency (change it in one place, you need to worry that it changes also in the other).