With the subsequent release of FileMaker 14, and FileMaker Go 14 in particular, the advantages of Perform Script on Server simply can’t be overlooked by anyone creating solutions within FileMaker Pro.
#FILEMAKER SERVER SCRIPT HOW TO#
Yeah, developer’s recognized it, but didn’t really know how to value its power. When FileMaker 13 was released, one of its sleeper features was Perform Script on Server. If you're interested in making this process happen as quickly as possible, then using Perform Script on Server is what you should learn to use. This video specifically covers how to restore the user context for processing a found set of data. That is, the proper layout and the exact same found set to be used for processing the data. One of the biggest issues with running server side scripts with Perform Script on Server is the fact that you need to know what's happening when the script is running, how to troubleshoot and most importantly, how to replicate the current user context. While there are still various limitations, such as the number of simultaneous server side scripts, it's absolutely something that any serious FileMaker developer needs to know how to use. With the addition of Perform Script on Server we gained a REALLY BIG performance boost by being able to perform most any script on the server. Many times, FileMaker does it's best to optimize whatever is being done, but it's still not as fast as executing certain things directly on the server.
#FILEMAKER SERVER SCRIPT FULL#
The processing of a script, client side, always had, and still does, make a full round trip for all kinds of these processing activities. Prior to FileMaker 13 we never even had the option of performing scripted tasks where the data actually exists. I hope the content helps you advance your level of FileMaker development knowledge. This code can be used in many more places than just duplicating related record sets.
I also cover a method which uses JSON in order to replicate a set of related records. This video shows you how to write a script which will duplicate related record sets and do so using the method of exporting and importing. However, I didn't show the other methods possible and we also got some newer features which allow us to do things even more differently.
In 2018 I covered a method using a dedicated table occurence which is perfectly viable today. There's also the very important choices of which method you're going to use. The trick with creating scripts which will also work on the server side is being very specific with the context of things. Of course, it makes total sense that you'll get the best speeds when working with the data where it's most accessible. Knowing how to take advantage of Server Side scripting within FileMaker is quite critical when you want the best performance possible.