Filter data in a Filemaker 10 portal

Is it possible to create 3 portals on one layout at the same time with different data from the same table by attaching a filter to each portal. Not by using a global value or a GTRR button.
Table = expenses
Desired field for filtering = type
One portal each for 'travel', 'household', 'medical'
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will LovingPresidentCommented:
FileMaker Pro 11 and later have an option in the Portal Setup dialog which allows you to specify a calculation to filter on. This would allow you to have three portals, all based on the same relationship, and filter them differently.

To do this in Filemaker Pro 10, the simplest method, without using a Global field as a switch, is to create three relationships to the Expenses table, on for each "type" of expense. You'll need to created Global fields in the Parent table for each "type" value and then include that as a second predicate (condition) in the relationship.

Alternately, you could have a single relationship and portal and just a Global Field called Type_Select with Radio buttons for each type, including an "All" Type if you wish. The user can then switch between views. The Global field is included as a second predicate in the relationship. If you want the "All" option, you'd need to create a calculation field in Expenses that has "All" on one line and then the "Type" value on a second line.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andrew AngellCo-Owner / DeveloperCommented:
I'm pretty sure what you would need to is create separate table occurrences that would show only each type and then bind the different portals to the different TO's accordingly.

A common practice is to create the TO's based on relationships to static, global fields.  For example, you could create a new field in the expenses table called relationship_travel and set it as a global field with the value "travel".  

Then you can create a new table occurrence for the expenses table called expenses_travel and setup the relationship for it where expenses::relationship_travel = expenses_travel::type.

This should give you nothing but travel records in the expenses_travel table occurrence, which could then be bound to a portal that you wanted nothing but travel records to show up in.

Then you'd repeat the process for the other two types.
maryj152Author Commented:
Thanks for the info. Our database is built on an old version of Filemaker and I understand that we can not update to newer than version 10 with out loosing functionality.
I have created 3 tables, one for each portal and will have to be satisfied with that. I am trying to clean up/streamline the database but not making much progress.
Angular Fundamentals

Learn the fundamentals of Angular 2, a JavaScript framework for developing dynamic single page applications.

Will LovingPresidentCommented:
You really shouldn't loose any functionality converting to 11 or 12, especially if you are already at 10. The simplest way to test this is to download the 30-day trial version of 12 and convert the files to FileMaker 12 (.fmp12) format.

The one thing to be aware of whenever you do a version convert in FileMaker is to convert ALL files at once. The simplest way to do this is to select all files to be converted and drag/drop them onto the FileMaker Pro application icon. And you don't need to rename the old files, just skip that step. (If convert multiple files that are related individually, connections such as relationships and script links usually get broken).
maryj152Author Commented:
Thanks for the advice. Lots of changes going on here. Don't know if we will be keeping Filemaker for the database or not. I am trying to organize it for keeping while someone else will be making the final decision.
Will LovingPresidentCommented:
If your database was originally pre-FM7 and you have multiple files, each with a single table in it, I've written an EE article on how to consolidate multiple files into a single one, which makes management and future development MUCH easier. There are reasons for using separate files with FM7 and later but they mostly for developers doing high end projects.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.