Filemaker server side scripts11/6/2022 ![]() ![]()
Using PSoS is simply a matter of understanding what’s happening server side and knowing how to troubleshoot. Need to communicate with other web services via ODBC, SQL, REST, SOAP (pick your acronym)? Want to send bulk HTML email using an online service like Amazon’s SES mail sending? Need to automate a routine import which normally task just a bit too long? Because of what you can do on the server side, there are few, if any limitations. While certain script steps like Export Field Contents cannot be used with Perform Script on Server, there is a wealth of functionality which can be harnessed through the use of server side plug-ins. If your FileMaker solution has any number of users, beyond a very small number, then the performance gains can be quite significant for certain tasks. 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. 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 side scripts 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. #Filemaker server side scripts code#This code can be used in many more places than just duplicating related record sets. Back with version 12 or 13 (they can't remember exactly which version it was working in), they had a script that they ran on the server daily after hours to check things. I just joined this company recently and am working with their Filemaker program trying to fix up their Scripts a bit. I also cover a method which uses JSON in order to replicate a set of related records. Missing scripts with Server Side Scripting. 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. More… Pausing Scripts Executed by FileMaker Server 11 or Previous.Knowing how to take advantage of Server Side scripting within FileMaker is quite critical when you want the best performance possible. But what do you do when you need to pause a script being executed by FileMaker Server when you are using an earlier version of FileMaker? In other words, export, pause, and then import.įor FileMaker 12, you can simply use the Pause/Resume Script step because it is compatible with FileMaker Server. The answer, if you can’t tell where I’m heading, is to place a pause between these two script steps. As a result, the script would either throw an error or simply not complete the process as expected. I found, for example, that if I created a server-side script which contained an export/import process, there were times that the script didn’t seem to wait for the export to complete before trying to import from the file created by the previous step. Over the years, I’ve had to deal with the need to slow down a script being run by FileMaker Server many times and thought I’d write about how I do it. The solution was to pause the script in question. I came across a blog post recently which focused on an issue where a script, run from FileMaker Server, kept failing. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |