Anyone know how to display grandchildren on parent layout with an on the fly filter feature?

I have set up the base of this and attached. I'm obviously missing a piece, but don't know what it is or how to implement.

Any help?

I appreciate it!

Cheers!

FilterGrandchildrenDemo.fp7.zip

I do have this "working" by a global field in the AssignmentsTable placed on the ProjectsTable layout.

But am wondering if this is good technique and if there is a better way to do this???

Proposed working demo attached.

THANKS!

FilterGrandchildrenDemo02.fp7.zip

Hi Randy!

How many Tasks do you think would ever exist on a single ProjectParent? If under a few hundred, I would not hesitate to use a filtered portal instead (please see modified file). By using filtered portal instead of filtered relationship, you can eliminate some graph clutter.

In this instance, because of the perspective, we can't simply place the Assignments::Title_Assignment field in the Tasks portal because it will evaluate only the first 'parent'. So I attached a value list on your TasksGrandChild::ID_Assignment field so we can easily display the Title_Assignment.

Value Lists can come in handy in situations like this and sometimes I will create a value list ONLY to provide the 'secondary value list value' without having to create a direct relationship or add a calculation.

UPDATE: I did not remove the unnecessary table occurrences.

FilterGrandchildrenDemoMOD.zip

By using filtered portal instead of filtered relationship, you can eliminate some graph clutter.

You won't hear me suggest this very often. I am not sure exactly where that 'break point' would be - it would depend upon several factors but a few hundred records (I would WAG) would be fine and if you only have 50 or so max (average) then I feel it would be the best alternative.

Hello LaRetta!

I never really thought of using value list just to provide the secondary value. I have done this before, but unknowingly. Great tip!

Yes, in this particular system, Task per ProjectParent would rarely reach 50, and may never reach 100.

So, unfortunately, the company using this database is STILL using FileMakerPro 10! So I can not take advantage of the filtered portal, I must go the filtered relationship route.

Thank you for chiming in!!! :-)