![]() ![]() This saves us from the recursion limit but does not gain us any speed improvements (and in fact may be even slower).įileMaker 13 introduced the ‘List of’ summary field, which is a much faster way of collecting field values from found sets. Instead of doing this work via a custom function, we could loop through the records and collect the values. (The limit for tail recursions is 50,000.) The second is that it’s slow when the size of the found set is large. This approach has two limitations: The first is the 10,000 recursion limit that FileMaker has for custom functions when doing additive recursions. If ( iteration < Get ( FoundCount ) CollectValues ( field ) ) $i_forColValCF = If ( iteration < Get ( FoundCount ) $i_forColValCF ) $i_forColValCF = If ( IsEmpty ( $i_forColValCF ) 1 $i_forColValCF + 1 ) I used to recreate found sets on the server by collecting the primary key values using a custom function and then creating a find request for each value in the list, but this approach does not scale well. Since it runs on the server, the current context (including the found set) is lost and has to be reconstructed. A good example of this is when the Perform Script On Server (PSoS) step is used. ![]() There are certain situations in FileMaker development where the current found set needs to be recreated. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |