(Or marks it as completed plus replaces the stored file with a reference whatever suits you.) Set up a server script that runs, say, every five minutes, checks if there are any new records in this table, exports each record using the Export Field Contents script step, and deletes the record.

Create a “File” table with a container field.

UPDATE: To initiate the process on client and have it to save the file on server you need to somehow tell the server that there's a file it needs to save. Give this shell script another privilege set and have it to move the file to the

to point to /my/path on disk My Disk you'll write: filemac:/My Disk/my/pathĮxport into the Documents folder and rewrite the schedule to run shell script after You start the path with a platform prefix: filemac.Į.g.On Mac all FileMaker paths virtually start in /Volumes.But if it worked, then the path will be like this: Try to give FileMaker correct privileges for the target folder. If this works, then the script is OK and you only need to work around the privileges issue. This should export the file into /Library/FileMaker Server/Data/Documents. Try to write a separate server script and export into the following file: 'filemac:' & Get( DocumentsPath ) & 'myfile.xml' The client has the same privileges as the current user, while the server runs as fmserver:fmsadmin and can only access its own directory tree in /Library/FileMaker Server. FileMaker client runs under different OS privileges than FileMaker Server.

Filemaker pro server