
First, this technique uses the Perform Script on Server script step (a.k.a.Now let’s get to building this thing! Can we build it? Performing the script on the server avoids hair-pinning and doubling the amount of network traffic required. Normally, you would need to download all PDF files to the client via container fields, export them somewhere where they can be manipulated and then combined and finally re-uploaded the result to another container field. It also does not matter if you have external storage enabled for container fields, since FileMaker takes care of that part for you.Īnother benefit is the savings in networks latency if this action were to be performed on the client. Encode/decode Base64 to create text files on the flyīy performing this script on the server, there is no need for third party plugins to be installed on the client, which also makes it compatible across the platform and supports FileMaker Go and WebDirect.Integrating with a 3rd party server-side program.



The script sets up some parameters, including the Folder Name and some parameters for the error Notification, if the folder already exists.

Finally paragraph returns are inserted so AppleScript can read the lines correctly. Quotations marks are being escaped, because they confuse FileMaker, but AppleScript requires them. This looks a little complicated, but all that is really happening is that the variables in the AppleScript are being replaced with values from FileMaker.
