Coffee cups indicate the complexity of a file, tip or article. One coffee cup is the easiest and three is the most advanced.
To download a file, click on the green arrow icon next to the listing. If there are no coffee cups
or platform icons, the listing may be an article, Quick Tip, Knowledgebase or bonus file.
The standard approach for a portal that isn’t filtered is to use aggregate functions like Sum or Count. Since aggregate calculation are defined in Manage Database, they are considered structural or schema level. Filtered portal are defined at the layout level, meaning a portal based on the same relationship on two different layouts can have to different filter formulas or even no filter at all. In other words, there’s no communication between these two areas of FileMaker nor could there be. There are two common methods for aggregating a portal that has a filter portal records calculation attached. The first is to use a summary field defined in the child table along with a one row version of the filtered portal encompassing the summary field. It sounds kludgy but it’s been that way since filtered portal were introduced in FileMaker Pro 11. The other method uses the ExecuteSQL which was introduced in FileMaker Pro 12. ExecuteSQL allows tables to be queried without a relationship, making them a great technique for aggregating filtered portals.
Tip File
