#Filemaker baseelements github pdf#
#Filemaker baseelements github pro#
#Filemaker baseelements github free#
#Filemaker baseelements github windows#

Remember that we passed in the Persistent ID by using “Get ( PersistentID )” from the client. To create a folder in the Documents folder, we can use some standard functions to calculate the correct path: Right ( Get ( DocumentsPath ) Length ( Get ( DocumentsPath ) ) - 1 ) & $_persistentID By creating a separate folder for each user, using their Persistent ID, each user’s folder will only contain their documents. Working Directory in a Multi-User EnvironmentįileMaker Server can write to the Documents directory in the FileMaker Server folder on the server.

#Filemaker baseelements github free#

Again, you can use any method you like but feel free to examine the custom functions used in the sample file. Personally I like this syntax because it follows syntax used in other languages as well, such as javascript functions.

We also have a custom function in the script that we are calling to automatically create variables defined in the script name that look like parameters. “#t” is a custom function that prepares the parameter. It ends up looking like this: Perform Script On Server In our example, we use a custom function to handle quoting and to make it easier to write. Once we have those, we can unpack them in our server-side script and use them. The objective is the same, to hand off multiple parameters to our script running on the server. At Soliant, we have several custom functions to aid in making this easier, but you may substitute whatever method you prefer. Note: there are several ways to pass multiple script parameters to a subscript. We pass in the Persistent ID of the computer or device where the script is running, and the current ID of the parent record we are on. Since the script running on the server needs to know about the current context we are working in, we need to pass it a couple of script parameters. The client’s persistent ID can be used as an identifier for each users device that is connected to the server. Once that is done, we can work in that directory until done and then clean up after ourselves by removing the folder at the end of the script. To avoid multi-user conflicts that will potentially use the same file names to when performing the scripts, we can create a unique folder on the server that represents the user. PSOS Setupįor the script that runs on the server, exporting files to the Documents folder that resides in the FileMaker Server Data folder is the safe place to put things and avoid potential permissions issues, so we will use that. All the pieces involved will also work on OS X, but the shell scripting would be different.

#Filemaker baseelements github windows#

PDFtk also supports handling different size pages of PDFs and combines them as a single document.Īlso of note, this example uses FileMaker Server installed on Windows Server. PDFtk is also capable of doing much more than combining PDFs, but for this example, that will be our end result. This version provides a command line interface which is fine for our server-side implementation.

Finally, we will be integrating with a freely available and popular server-side program for manipulating PDFs, PDFtk server.

#Filemaker baseelements github pro#

Also recommended is the use of FileMaker Pro Advanced for development, but this is not a requirement. This means that once we are done, clients won’t need to have the plugin installed, but for development, we will also have it installed on FileMaker Pro.

Next, we will be using the now open source Goya BaseElements (thanks Goya!) plugin installed on the server.

PSOS) so we already assume that your environment includes FileMaker Server.

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.

#Filemaker baseelements github pdf#

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.

Performing command line scripts on a server.

Some of the techniques used in this example: I believe this is a good example, in part because it combines several techniques, each of which has value.