Because the data from both id_path and $$sort_dictionary have already been downloaded to the local machine, sort_key can calculate very quickly.ĭrag-and-drop arbitrary sorting and reassignment Stay Tuned!.The portal is then set to sort by sort_key.For example, an id_path with “000001 000034 000052 000076” would become “Plants Vegetables Roots Carrots” on the fly, using the values from $$sort_dictionary.A sort key field ( sort_key) is calculated on the fly by replacing IDs in the record’s id_path with the corresponding sort value from $$sort_dictionary and padding it with zeros if it’s a number field.Before sorting, all related values of sort_dictionary are copied into a global variable named $$sort_dictionary using the List() function.A dictionary field ( sort_dictionary) of record id’s and sort field values is created in the data table.This FileMaker Pro hierarchical portal filtering file demonstrates an approach that combines the light footprint of a dynamic approach with performance closer to that of a static approach. However, this would very quickly become so slow as to be unusable. Dynamic Approachįor very small data sets, you could make the path field an unstored calculation and have each record calculate up the path chain dynamically. Also, whenever a record was edited, all descendant records would need to have their sort fields updated. Each additional field that you wanted users to be able to sort by would need a similar field. For example, if you wanted to sort by name, you’d have to create a sort_name field that contained “Plants Vegetables Roots Carrots”.
The most straightforward approach would require creating an index “path” calculation for every field that you might want to sort by.
WordPress Maintenance & Support Packages.
0 kommentar(er)
