In your filter calculation, put the simpler conditional statements at the beginning of your “and” statements.Here are a couple of things you can do to maintain better performance: In cases where there are very large numbers of related records and/or the portal filter calculation is very complex, you may notice some performance issues. With portal filters, FileMaker is checking each related record individually and applying the filter criteria to it. However, they had one advantage: they took advantage of FileMaker Pro’s built in indexes to retrieve the appropriate results. These tended to be more complex and difficult to build, and they had some serious limitations that can now be transcended with FileMaker 11 Portal Filters as outlined in this article. Prior to FileMaker 11, portal filters were generally built using relationships (see Google-Like Searches Through Relationship Filtering). Taking the above example one step further, lets say we want to have a popup menu for status, and separate search fields for task name and task description. Example 2: One Pop-up and Two Open Text Searches Or if, for instance, Globals::Search_Status is set to “Open” and Globals::Search_Text is empty, we will see all task records with a status of open. The result is that if the filters are empty, we will see all of the records. Notice the use of the IsEmpty function to effectively ignore the filter if it is empty. Here’s the calculation: ( IsEmpty ( Globals::Search_Status )įindWordPartsInText ( Globals::Search_Text Task::Title & ¶ & Task::Description 1 ) ) In this case, we will want our filter calculation to evaluate to true if the Globals::Search_Status field exactly matches our status field in the task table (Task::Status), and our Globals::Search_Text field matches one of the words in the task title (Task::Title) or the task description (Task::Description). We will assume that the pop-up menu field is named Globals::Search_Status and the text field is named Globals::Search_Text. The screen shot at the beginning of this article shows a portal of tasks with dynamic filter criteria to filter results by project status (a popup menu with fixed values) and an open text field which searches multiple fields. Here are a couple of examples: Example 1: Calculation for One Pop-up field and one open text field: This calculation will look different depending on the number of filters and the type of filters that make up your criteria. So, the entire expression will only evaluate to true if all filters contain a match. You will expand this calculation by adding a conditional statement for each of the filter fields and join all of these statements with the “and” operator. The calculation will be an expanded version of the one in Step Three in Dynamic Portal Filtering While You Type. Step Three: Set the portal filter calculation If you have already created this function in your solution, you can skip this step. This step is exactly the same as Step Two in Dynamic Portal Filtering While You Type. Alternatively, you can create a single search field with multiple repetitions. Except that you will create one global search field for each filter criteria. This step is almost exactly the same as Step One in Dynamic Portal Filtering While You Type. Step One: Create the Global Search Fields Create the script (6 or more script steps depending on number of criteria).Set the portal filter calculation (copy and paste with some modifications).Create the custom function (copy and paste).The main differences are that the filter calculation and script become slightly more complex. This project consists of 5 basic steps which are similar to those in the Dynamic Portal Filtering While You Type article. It’s recommended that you read that article first if you haven’t already. Note: This article builds on a previous article, Dynamic Portal Filtering While You Type.
0 kommentar(er)
