Help

Creating scripts to automate tasks
F
ILEMAKER PRO HELP 429
3. In the Manage Scripts dialog box, click .
4. Open the file that contains the script(s) you want to import.
5. In the Import Scripts dialog box, select the script(s) you want to import.
If one or more of the scripts you’re importing refer to other scripts, make sure you select and
import all the referenced scripts at the same time. For more information, see the Notes below.
6. Click OK.
The Import Summary dialog box appears.
7. Click Open Log File to view the import log file, or click OK to close the Import Summary
dialog box.
If FileMaker Pro reports errors, follow the steps in Creating and editing scripts to correct the
<unknown> references in each script. During the script import, FileMaker Pro checks all
references to fields, layouts, other scripts, files, and so on, in each imported script. References
must match exactly to be included in the import. If a referenced object is not found,
FileMaker
Pro flags it as <unknown>.
8. Close the Manage Scripts dialog box.
Tip You can import scripts into a folder by selecting the folder, then clicking .
Notes
• The match for field names is not case-sensitive.
• When importing a script that references a related field, the fully qualified field names must
match identically, including the names of the tables as they appear in the relationships
graph.
• When importing script steps that contain calculations (for example, If, Set Field, and, Insert
Calculated Result), if FileMaker
Pro cannot match all items referenced in the calculation
(i.e. tables, fields, or custom functions), the calculation is commented out (using ‘C’ style
comments).
• When importing scripts from single table files, you can avoid most of these naming errors by
making a copy of the file containing the script you want to import. In the copied file, rename
the table to match one of the tables in your destination file, and import the script from the
copy. Script steps that refer to identically named fields and layouts in both files will import
properly because the underlying table in the source file has the same name as a table in the
target file.
• When importing script steps that contain more complex information (for example, find
requests, sort order, import field order, and export field order, etc.), FileMaker Pro discards
any missing field references.
• To import a script, you must have access privileges in the source file that allow you to
modify the script.
• The option Run script with full access privileges is only imported when the user
performing the import has logged into the target database with full access privileges.
Related topics
Managing scripts using folders
Deleting a script
Planning a script