filemaker pro 14 stops working when saving scripts

I have adjusted my path to include a subfolder for today’s date:Īnd that’s how you automatically create directories in a file path. If the folder exists, FileMaker will simply save the file without overwriting the directory. In the Save Records as PDF Script Step, note that Create directories is ON.Īfter I run the script, I now have a folder on my Desktop called PDFS and my file is stored. For information about individual script triggers, see FileMaker Pro Help.

For example, if a FileMaker WebDirect user clicks a field that has an OnObjectEnter script trigger, the trigger is activated. In this script, I set my Export path to the variable “$path” and designate the PDF to go to a folder on the Desktop, called PDFS. Here’s how it works: At the time of the sale, the system prompts the store employee to ask if they will provide an online review. Script triggers As in FileMaker Pro, user actions (such as the user clicking a field) and scripts can activate script triggers in FileMaker WebDirect. In previous versions, if the folder is not available when you export, you would get this panic-inducing error:įileMaker 17 allows us to ensure the directory is always there with the “Create Directories” option in the Save/Send As Script Step. In my scenario, I want to save a PDF of a layout to a folder on my desktop called “PDFS.” As you can see that folder does not exist.

Filemaker pro 14 stops working when saving scripts