Script Steps Reference

Table Of Contents

FILEMAKER SCRIPT STEPS REFERENCE 79

Description

You can set the export order before adding this script step, or perform the step with a dialog box so

a user can set new criteria. Export Records exports all the records currently being browsed. If you

want to limit the set of records you're exporting, use a find request before using Export Records.

When you include this script step in a FileMaker Server scheduled script and you do not select

Perform without dialog in the Edit Script dialog box, the text (NOT compatible) appears after the

script step. The script, however, will run. The behavior will be the same as if Perform without

dialog was selected.

Notes

• When using the Export Records script step or Import Records script step in a

FileMaker

Server scheduled script, keep the following in mind:

• Any specified file must be in the FileMaker Server Documents folder, the temporary

folder, or a child folder of either the FileMaker

Server Documents folder or the

temporary folder. For example, the following are all valid paths for file.csv:

<Documents>/file.csv

<Temporary Path>/file.csv

<Documents>/Folder1/file.csv

<Temporary Path>/Folder1/Folder2/Folder3/Folder4/file.csv

• Any path specified that isn’t a complete path to the file (for example, anything other than

/Library/FileMaker Server/Data/Documents/<0 or more directories>/<filename> ) is

evaluated as being relative to the temporary path.

• Any paths that include “..” are considered invalid.

• For FileMaker Pro, if an absolute path is not specified in a script that will be executed from

FileMaker Pro, the path is assumed to be relative to the location of the database file from

which the script was run. For example, if a script containing the Export Records script step

is run with the pathname

file:/export.tab, and the file running the script is /MyFiles/

Library/Books.fp7, the exported file will be created as /MyFiles/Library/export.tab.

• If you are using a calculation that generates the file path for the XML file, you need to use

the format used by the operating system for the the full path. For example, the following are

valid paths if you are using calculations to generate the path for the XML file for Windows or

Mac

OS:

Mac OS: /Volumes/VolumeName/directoryName/fileName

Windows: driveletter:/directoryName/fileName

If you are providing a cross-platform solution, you can use the Get(SystemPlatform) function to

identify the current platform and use the correct format for each platform.

Examples

Go to Layout ["Layout #4"]

Export Records [No dialog, "Contacts"]