However, a server-side script can be stopped if:Ī server administrator stops the script, which appears as a separate client that can be disconnected in Admin Console for FileMaker Server or FileMaker Cloud To help you troubleshoot problems, errors are also written to the event log on FileMaker Server and FileMaker Cloud.Ĭlients can’t stop server-side scripts. Use the Get(LastError) function in server-side scripts to handle error conditions. Server-side scripts can’t cause a FileMaker client to display alert messages as when scripts are run on clients, so server-side scripts always perform as if the Set Error Capture script step were set to On. Scripts run by a schedule use the account specified in the schedule. Scripts run by Perform Script On Server use the same account as the client. Additionally, when a client uses the Perform Script on Server script step to run a script that performs sub-scripts in another file, the file containing the sub-scripts must already be opened by the client. Server-side scripts can use the Perform Script script step to perform sub-scripts, which also run on the server, only if those sub-scripts are in files on the same server. Therefore, the OnFirstWindowOpen script trigger is activated when the script starts and the OnLastWindowClose script trigger is activated when the script ends. Running server-side scripts opens and closes the files that contain the scripts. If records are locked by a client, server-side scripts cannot access uncommitted data or change the contents of those records. To use the Import Records or Execute SQL script steps with an ODBC data source that uses the server’s DSN To enable FileMaker Go clients to perform tasks that require plug-ins, which are supported on FileMaker Server but not in FileMaker Go To offload long-running tasks from slower clients to a faster server To improve performance by reducing the amount of network traffic between the client and server You can also refer to the Compatibility table for each script step in Script steps reference. Script steps that aren’t supported appear in a different color. To see which script steps are supported by the FMSE, in the Script Workspace in FileMaker Pro, open a script, click, then select Server. # Continue with script steps supported by the FMSE For example, the Open File script step is unsupported by the FMSE, so the following script running on the server will skip that step and return "unsupported" in the result. The Get(LastError) function after a step in order to check whether that step is unsupported, then perform supported steps instead. To handle unsupported steps, your script can use the If script step with: However, attempting to perform an unsupported script step returns error 3 ("Command is unavailable"), skips the unsupported step, and continues to the next step. Many script steps are supported by the FMSE. Server-side scripts run the same way regardless of how they’re started, except for the following:Ī client using the Perform Script on Server script step has the option to wait for the script to complete on the server and use the Get(ScriptResult) function to capture the result.Ī schedule can be set to end if the running script exceeds the specified time limit.
#Filemaker server side scripts password
The files were already opened by the client that started the server-side script, or set up with an account name and password specified in the file’s File Options dialog box (FileMaker Pro only) Support script parameters and script results up to 1 million charactersĬan access other FileMaker Pro files only when both of the following are true: The server-side script can use that information in script steps like the Go to Layout script step and Perform Find script step to specify which layout and found set to act on. You can pass information about the client’s context to a server-side script by using the script parameter in the Perform Script on Server script step. As a result, server-side scripts:ĭon’t have the client’s context (current layout, found set, sort order, record, global field values, and local or global variable values) The FMSE is a client that runs each script in a separate session on the server.
The Perform Script On Server script step in a script running on a clientĪ schedule (see FileMaker Server Help or FileMaker Cloud Help)Ī script started by either above method is run by the FileMaker Script Engine (FMSE), a component of FileMaker Server and FileMaker Cloud. However, you can run a script on the server (a server-side script) by using: Scripts in files hosted by FileMaker Server and FileMaker Cloud normally run on the client. About running scripts on FileMaker Server and FileMaker Cloud
0 kommentar(er)
