Child report table on Parent record
So I need an answer to 2 questions here: 1) How do I get the child report table that appears on the parent record to extend all the way accross the screen. I have attached a pic. 2) Is th...
Forum Discussion
Geoffrey,
Combining multiple variations of text from a child to a parent via a reverse relationship will not work, because you'd have to account for every variation of the child. And the number of children. So if you had 10 child cards, you'd have to have 10 reverse relationships, and then a master formula to recombine them.
Additionally making each of those sequential relationships will require about 4-5 new fields for each of them. This will take a huge hit on your app performance.
My recommendation:
On your child "Cards" table, create a summary report that combines like values in the text field.
>
Then make a report link on your parent table, and use that summary report on the form.
>
This should give you the summed text values, and display them on the form.
I know its not perfect, but from what I can tell this might be a good option.
p.s. You might consider addressing how they input the multiple items. That sounds like it could be handled differently, which might give you better reporting.
Combining multiple variations of text from a child to a parent via a reverse relationship will not work, because you'd have to account for every variation of the child. And the number of children. So if you had 10 child cards, you'd have to have 10 reverse relationships, and then a master formula to recombine them.
Additionally making each of those sequential relationships will require about 4-5 new fields for each of them. This will take a huge hit on your app performance.
My recommendation:
On your child "Cards" table, create a summary report that combines like values in the text field.
>
Then make a report link on your parent table, and use that summary report on the form.
>
This should give you the summed text values, and display them on the form.
I know its not perfect, but from what I can tell this might be a good option.
p.s. You might consider addressing how they input the multiple items. That sounds like it could be handled differently, which might give you better reporting.
- This doesnt work in my case because a summary report doesnt allow me to summarize a formula text field (unless I am missing something?) The option for that field doesnt even appear on the drop down
- Use the text values for the grouping or rows, not the summary
- Ok i'm with you. the summary report actually looks ok. Just on the report link, not sure how to display this report on the parent table through a report link field.
- Geoffrey,
You will want to edit the field properties for that report link, and set the 'target'.
In the image attached, this is a report link field on the 'projects' table and it is displaying related child records on the 'time entry' table. - done
- I am needing to this also, but think i am missing something. you state "On your child "Cards" table, create a summary report that combines like values in the text field." what do you mean "in the text field"? i have a parent table that has multiple children, want to display all the children in in a report of the parent. Can you please give me more detail?
thanks,
Jeanne - Jeanne
How many children would you need to float up data from up to the parent record. - a parent will have at least one child but can be up to 10. avg would probably be 3 or 4.
thanks for you help! - Here is an answer from a previous post which you can adapt to your situation.
If you have a large app with say over 100,000 records in the relevant tables, then performance could be affected by all the looping. But if you are dealing with just thousands of records you should be OK.
The way to do this is with as many "reverse relationships" as you guess will be enough to cover off 99% if the situation.
So, let talk about Operators. One Job has many Operators. Make a summary field on that relationship of the Minimum of the Record ID# of Operators. Call it [Record ID# of Operator 1].
Then do a lookup of that down to the child Operator table as we will need it later.
Then do a new Relationship where one Operator has many jobs. For the reference field (the field on the right side), use that new Summary field called [Record ID of Operator 1]. Get rid of the extra fields that get created on the left side of the relationship (Add Operator and that report link field). Do a lookup from the Operator down to Jobs and bring in the Operator Name and call it Operator 1.
Wonderful, the Job now knows the first Operator.
Now, make a duplicate of that summary field, but in the duplicate add the extra condition that the [record ID#] is greater than the [Record ID# of Operator 1]. Call it [Record ID# of Operator 2]. Do a lookup of that field back down to the Child Operator table as we will need it later.
Now, in making that duplicate, conveniently, you will find that it duplicated the reverse relationship so now do a lookup in that relationship of the operator name called it [Operator 2]. Wonderful again, we now have Operator #2's name on the Job Record.
Then make another duplicate of that summary field and just keep going, each time changing the filter so that the record ID# is greater than the previously highest record ID of Operator.
In the end say you collect the names of the first 4 operators on a job, so then just string them together in a formula like
List ("\n",
[Operator 1],
[Operator 2],
[Operator 3],
[Operator 4])
and put that concatenated field list on your report. - have a little trouble following , also i made my own unique key, can't seem to do what this is calling for. Are there any more detailed instructions?
thank you for your help!
