FileMaker Finds In Portals ( unstored parent match fields )

From Dwayne Wright PMP
Certified FileMaker Developer

TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

Please Note: If you are viewing this page in a news feeder, the images may get munged up a bit. For the best experience, please visit the journal directly by clicking (here). 

In this example, we want to illustrate the need to have a relationship parent match field be stored in order to do a portal search. Under the hood, we have two relationships setup. In the first relationship, the parent match field is a stored value and it is not in the second relationship.

We have setup two tabs and placed a portal on each. The first has a portal that has a stored field as the parent match field for the relationship. We scripted a find for any student that had any test score equal to or above 90. In this layout, you can see the search works with the example records. There are three records total and one of them doesn’t make it into the found set.

In the second tab, we created a calculation field for a parent match field. It is a very simple calculation, it simply is equal to the parent key in the tab that works... except ... in the storage options we disabled the fields ability to be indexed. In other words it cannot be stored and this makes searches in the portal impossible.

An example file can be downloaded by clicking (here)
More info about the author and FileMaker in general, contact me at

© 2008 - Dwayne Wright -

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.