Filemaker and Perform Script on Server

Server-side Script Execution with PSOS (Perform Script on Server)

Perform Script on Server (PSOS) is like teleportation for your scripts: instead of running on the user's machine, your script jumps over to the FileMaker Server and runs there at warp speed. This is a huge win for performance — you offload heavy lifting from the user interface and let the server do the hard work. It's like having a backstage crew making magic happen while the user enjoys a smooth, uninterrupted experience on the front end.

When should you unleash PSOS? Think big: generating detailed reports, crunching lots of data, or sending out emails like a boss — all without slowing down the user. It’s your go-to for anything that makes your CPU sigh.

But wait! Before you send your scripts zooming to the server, there are a few things to keep in mind:

- Set the context: PSOS doesn't read minds. It usually starts at the default layout (which might not be helpful). So make sure your script navigates to the correct layout to get the right context for data access. Without this, the server’s basically flying blind.

- Pass global data: Globals? What globals? The server does not know the globals you are using on your client session side. Never forget that a server-side script is running in its own isolated session, knowing nothing about the current client’s context — that includes global field values and global variables. If your script depends on them, pass them in explicitly as parameters or fetch them again on the server. Otherwise, the server will be working with a blank slate.

- Define the found set: The server doesn't automatically know what records the client had found. You have two options: either redo the search on the server (by passing the criteria), or send a list of IDs so it knows exactly which records to deal with (kind of like sending coordinates for a drone strike).

Real-life example: A user clicks "Generate Report." Instead of locking up the UI for minutes, you trigger a PSOS script that swoops in, gathers the data, runs calculations, and spits out a PDF — all server-side. The user? Still clicking around like nothing happened. Bonus: by disabling Wait for completion, the script runs quietly in the background, like a ninja.

In newer FileMaker versions things get even cooler: Perform Script on Server with Callback lets you run a follow-up script on the client after the server finishes its work. It's perfect for things like "Hey, your report is ready!" pop-ups or refreshing data after a background task.

Heads-up: PSOS isn’t for everything. Don’t spam the server with dozens of jobs — it might start dropping plates. Use it strategically for heavy-duty tasks. Done right, PSOS can make your solution feel faster, smarter, and way more professional.

So go ahead — give your scripts a backstage pass. Let the server shine, and let your users enjoy the show!