What are the criteria you want to use to narrow the list?
The criteria comes from Policy Profiles which is a field names coverage
I have no idea what that means.
What records, in what TO, do you want to show up in the list?
I want the information coming into the Join Table from Table C to be filtered from information on Table B.
1 record in Table B is assigned to many records in Table C based on criteria in Table B.
I still don’t understand what you mean. There’s no “filter” you can apply from B -> C, because the relationship doesn’t join those two tables together. In other words, if I’m in the join table, the current record I’m on is joined to one record in B and one record in C (by definition). A join table is the “many” side of the relationship, so there’s only one record that matches on each side.
Why don’t you provide a couple of examples of what you mean - maybe include some actual data?
As far as I know, value lists are not conditional. In order to show a subset of table C, a portal can do the job with filtering.
1 of 1 people found this helpful
I think I see what you're trying to do now. You won't be able to do this with just the relationships you have. You can either:
1) Create a new TO for the destination and build a new relationship that includes the tab you're on (using perhaps a global field). Base the popover portal on that.
2) Use a Virtual List table in the portal instead of a direct relationship. Populate that via a script.
Can you share a dumbed down version of how to do #2?
Have you ever used / seen the Virtual List technique?
Good afternoon JammieSchmunk,
I hope your day is going well. You might also consider using the Selector/Connector method of creating a picker, assuming your policy records are all contained in one table. Good luck!
Bill, I've never even heard of Selector/Connector...
1 of 1 people found this helpful
That being the case, you might want to stick with #1 for now.
However, if you want to learn it, you can easily Google "FileMaker Virtual List". Several useful links pop up.
The basic concept is to define a table that has one or more unstored calculations fields in this form:
GetValue ( $$var ; row )
where "row" is a serial number corresponding to the record. You then store a return delimited list of values in $$var, which produces a "virtual" table - one where each record corresponds to a row in your variable.
This is a very powerful technique, covered in the FileMaker Training Series (Advanced). It allows you to build whatever list you want, via any means you like (looping script, calculation, ExecuteSQL) and then produce a series of records corresponding to the row.
Once you populate the list, you would then create a relationship between your current context (TO) and the virtual table, showing the records in a portal. But you're still not done.
You still need to create a script that fires when the user clicks on a row in the portal (assuming you want something like a pick list). Such a script records the value in that row, and then applies it however you need. You will often need two lists, one with the unique ID for the value and one for its description.
IOW - I don't have a "dumbed down" version of this to show. It's complex and involved to implement. However, once implemented, it's extremely flexible and can be moved from solution to solution with relative ease.