FileMaker 2023 introduces
Perform Script on Server with Callback, a new asynchronous method to execute scripts with FileMaker Server. Now we have a way for FileMaker Server to execute another script, a “Callback” script, when one script is done processing via
Perform Script on Server. It’s like calling your virtual assistant and instead of waiting on the phone for 5 minutes for info, they basically call you back when they are ready with an answer.
The end result is improved performance, better management of complex script workflow, enhanced user experience, and new possibilities for handling integration with APIs, email and services like Claris Connect.
Continue reading “FileMaker 2023 Perform Script on Server with Callback – Episode IV: Call Ya Later”
I often like to measure performance, because I am curious if some small change can lead to subtle, or maybe not so subtle, improvements. For the longest time my Swiss Army knife for measuring Claris® FileMaker® performance has been:
Continue reading “Finer Faster FileMaker Precision: Measuring How Long It Takes”
Get ( CurrentTimeUTCMilliseconds )
In looking back at our initial approach to logging FileMaker PSoS (Perform Script on Server) activity, I reflect back on a number of times where this has been extremely helpful. If you have come to rely on the benefits of PSoS then you also know some of its challenges — one of the biggest is debugging and monitoring how long sessions take.
Since FileMaker 16 introduced JSON, in new systems we’ve switched over to using JSON as the main way of exchanging data for parameters. Because we also use PSoS in new systems, we updated our method for PSoS Logging and this blog entry talks about the changes we made there and also restates the usefulness of this log.
Continue reading “Logging PSoS Activity: Episode III – Return of the JSON”
Managing Data You Use and Throw Out
We develop FileMaker applications because we want a place to store information for the long term. We track events, tasks, contacts, finances—FileMaker can track almost anything. To update information, the application might ingest a spreadsheet.
Continue reading “Speeding FileMaker Performance with Truncate Table”
Now more than ever we’re relying on Perform Script on Server (PSoS) to maximize FileMaker performance, so naturally a need arose for a way to proactively monitor how many concurrent scripts are being triggered. This type of logging helps us see if we’re reaching our maximum limit, or have a rogue script eating up processing power.
Continue reading “FileMaker Log Files: Episode VII – PSoS Awakens”
I hope that since our previous blog post you have been exploring the possibilities created by FileMaker’s Perform Script on Server (PSoS). This article is a continuation of the PSoS discussion and includes more cool things you can do with it, specifically running database imports on FileMaker Server.
Continue reading “What Are Your Imports Waiting For? FileMaker Perform Script on Server – Episode II”
Read the follow up to this blog post at What Are Your Imports Waiting For? FileMaker Perform Script on Server – Part II
Since the release of FileMaker 13 we have been exploring a new feature called “Perform Script on Server” (PSoS) and trust me there are many cool things you can do with it. I’m going to describe how PSoS works, how it’s best implemented, and how our tests show PSoS can drastically improve database performance, more than 100x in some situations. However, there are also a number of considerations before you run wild and convert scripts to execute via PSoS. So, I’ll cover these as well.
Continue reading “100x Faster – Flight Testing FileMaker Perform Script on Server – Episode I”