Records that won’t be displayed simply aren’t downloaded in the first place rather than being downloaded and filtered after the fact. This is because records are filtered at the relational level rather than the portal filter level. This requires more work to implement and more schema changes, but can result in improved performance in certain circumstances such as high numbers of related records or WAN deployments. The Classic approach to the hierarchical portal filtering technique uses a multikey in a global primary key field to filter records. It works to abstract the hierarchy logic using features like global variables and portal filtering, entailing fewer schema changes and requiring fewer changes after pasting scripts and fields.ĭownload Doug West’s version of Hierarchy Lite Demo The Lite approach on the hierarchical portal filtering technique focuses on ease of implementation. After reviewing them, we believe the original approach still has merit as one option to consider. Several alternate approaches have been developed in the interim for the hierarchical portal filtering technique (including a “lite” approach by my colleague Doug West).

Twenty years later, we decided to take another look and update it for FileMaker Pro 15. Way back in 1996/97, I developed my original hierarchical portal filtering technique using FileMaker Pro 3. Hierarchical Portal Filtering using FileMaker Pro 15 By Andy Persons WordPress Repair and Troubleshooting Services.WordPress Maintenance & Support Packages.

Filemaker pro 15 help