You will also need a simple custom function I use to point to field names rather than field values, called GetFieldNameOnly. The main purpose of your script is to manage a single global variable that is referenced in the four sorting calculations, in this example $$PersonSort. Notice that SortTextAscending and SortTextDescending take only The script By providing one of each you should be able to rebuild these calculations and make the fields specific to your data. Also be aware that there is only a 1 word difference between SortTextAscending and SortTextDescending and the same goes for SortNumericAscending and SortNumericDescending. Looking into these four calculations will require an understanding of JSON. Managing the data in those calculations will manage which field and which order that the portal will use for sorting. Inside the portal sort dialog, you don’t have the ability to sort by related tables, so you must create calculations inside the Person table. We will sort people records inside a portal on a company layout. I still believe I have broken the concept down to its simplest form and can explain the parts and how they work in a way that will easily translate to any custom FileMaker solution.įor the sake of this blog, I have set up a very straightforward demo file, made up of only two tables: Person and Company.
It was taught the concept from a coworker – who learned it from a blog or forum.
I would like to preface this blog by saying this is not a concept I invented. In this blog, I will walk through a consistent way to dynamically sort related data in portals, using the column headers. Realistically, you don’t always have the luxury of being in a simple 1 table list view. A common feature I like to provide on my FileMaker list view layouts is clickable headers that sort records based on that column.
0 kommentar(er)
