Then the sole function of the parent script is to pass the same parameters over to the child script that will be the one that will actually do the work. It may be a little more work to have your button or custom menu item first call a parent script, but it’s good to have that safety net. So, a best practice might be to always check to see if the current host application is FileMaker Server 13. The reason is that at some point if you open the file locally and execute those scripts you will get an error:Įrror # 3: Command is unavailable (for example, wrong operating system, wrong mode, etc.)
You can directly call a script to run on server from any layout object as a button, custom menu item, or script, but that might not be a good idea. There are only 3 places where you can directly call “Perform Script on Server” and you should only be using 1 of them…that is from inside a script using the Perform Script on Server script step. Otherwise you can easily overload your server/CPU and trash performance for the rest of your users. You should also take care in how many times you might end up calling scripts to run on server. So what good is PSoS, and how exactly does it work, you ask? PSoS is still incredibly useful, but you have to be careful when choosing to use it. Well, that puts the kibosh on simply converting every single Perform Script to PSoS. Once you have asked that script to run on server, any other sub-script can only be Perform Script and not Perform Script on Server. The Perform Script on Server can only be fired off by a client (FileMaker Pro/Advanced, Go or Web Direct). Although that sounds confusing when you first hear it, all it really means is: We can see that the Perform Script on Server step itself is not Server compatible. You can use the Show Compatibility pop-up menu at the bottom left of the Script editor window to see which steps are compatible. Well, not so fast! First off, not all the FileMaker steps are PSoS compatible. You may already be thinking: Why not always use PSoS instead of “Perform Script”?
And this new capability executes scripts so much more quickly on FileMaker Server. If you have users that connect to your database over a WAN and across the internet then performance is always going to be foremost in your mind. I’ll talk more about this later and give some great examples of how you could use it.
FILEMAKER PRO FOR MAC CAPACITY FREE
However, if you uncheck this option then the script is told to run on server and you are free to get back to doing whatever you want to do while the script does the work on the server. If this option is checked then you’ll have to wait till the server completes the execution of your script and all of its sub scripts before the parent script continues. You can specify a script to run using this method, and there is an additional option called “Wait for completion”. In FileMaker 13 we now have a new script step called “Perform Script on Server” (or “PSoS” for short). Getting Startedįirst, you’ll need FileMaker 13 for both server and clients. In a follow up blog post I’ll go into more detail and share some other exciting ways in which you can use PSoS to improve the FileMaker user experience altogether.
FILEMAKER PRO FOR MAC CAPACITY HOW TO
In this first of two blog posts I’ll talk about these results, as well as what you need to watch out for when using PSoS and how to work with these limitations. I have been rethinking solutions in light of this new capability and the results have been astounding. So, I’ll cover these as well.īefore I get started I’d like to give a big Thank You to the FileMaker engineering team for this new capability. However, there are also a number of considerations before you run wild and convert scripts to execute via PSoS. 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.
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.
Read the follow up to this blog post at What Are Your Imports Waiting For? FileMaker Perform Script on Server – Part II Introduction
0 kommentar(er)
