![filemaker pro 10 relationship between two databases filemaker pro 10 relationship between two databases](https://fmhelp.filemaker.com/help/13/fmp/en/images/create_db.8.2.3.png)
When it is "all", every one of the records will match regardess of status because they all match on the textstring "All".Ģ) Why does FileMaker allow relationships to be built with unindexed foreign keys?įileMaker's relationship diagram does not differentiate between which table is the local table and which one is the foreign table — it doesn't know where you will "be" when you try to use that relationship, and it doesn't care.
![filemaker pro 10 relationship between two databases filemaker pro 10 relationship between two databases](https://i.pinimg.com/736x/36/e7/10/36e710996e3f44049bb21e7bb82a0fef.jpg)
When it is one of the status values, the records that do not have that specific status will not match and will not show. As it already is in your situation: ItemFilterChoice is either going to be one of the "status" values, or it is "All". The switching is done on the local side instead. It has two values at the same time, either of which will match the relationship: the value in the field Status and the text string "All". The way you do "filterable" relationships that work is that the foreign side has to always reconcile to ALL values that will ever match, using a multikey calculation. It may be a glitch that momentarily, before FileMaker "notices" that the foreign side of the relationship is unindexed, it shows cached data or some such thing. NOTE: This is at least the second time I've seen someone claim to have seen data in a portal when the portal side is unindexed. Nothing will work because the portal side of your relationship is anchored by an unstored calculation field, and relationships do not work if the foreign (remote) side is not indexed. Despite the wording on your layout, choosing "New, Old, or Dead" also will not work.