![]() Place that aggregate calculation field on the layout beneath your portal to OrdersByDate, and you have a nice, neat interface to show you historical information about your customers. ![]() All you need is the previously defined relationship and the Sum aggregate function:Īs you change the values in DateRangeStart and DateRangeEnd, new orders would be found through the relationship and added up. Once you’ve selected a customer and filtered the orders to a particular subset by date, you probably want to know “How much did this customer buy during this time?” It’s a very simple calculation to create. Showing all orders for a customer for a given date range. This allowed us, for example, to create relationships from Customers to Orders that could be filtered by a date range. Way back in FileMaker Pro 7, when multiple tables per file were introduced, we also got the ability to define complex relationships with multiple “predicates” (sets of match fields) and comparative operators. Let’s examine the “problem” (because it turns out defining the problem requires more work than the solution itself). Fortunately, there’s an even easier solution for the majority of cases where you need to total up related records. Various solutions have been proposed using script triggers and merge variables, but they can require some foresight and maintenance. ![]() All of your calculations summarizing related records no longer reflect what appears in the filtered portal. ![]() If you’ve played with FileMaker Pro 11’s filtered portals at all, you may have discovered its biggest stumbling block: aggregate functions and related data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |