Help

Customizing files with FileMaker Pro Advanced
F
ILEMAKER PRO HELP 572
7. Click OK.
The Import Summary dialog box appears.
8. Click Open Log File to view the import log file, or click OK to close the Import Summary
dialog box.
Note The custom function you imported appears at the bottom of the list. If FileMaker Pro
determines this function is invalid in the context of the target file (for example, a dependent
function, field, or calculation is missing from the target file or the function contains an invalid field
type reference), the imported function is enclosed in comment characters (/
*<function_definition>*/). For more information, see
Custom Function dependency rules
(FileMaker Pro Advanced).
9. Close the Manage Custom Functions dialog box.
Notes
• If you import custom functions from another file, then click Cancel to close the Manage
Custom Menus dialog box, all changes you made while the dialog box was open are
discarded and the imported functions are removed from the file.
• If you cancel an import in progress before it completes, any functions imported before you
cancel must be manually removed from the target file.
• You can’t use a script to import custom functions.
Related topics
About custom functions (FileMaker Pro Advanced)
Using custom functions (FileMaker Pro Advanced)
Functions reference (category list)
Functions reference (alphabetical list)
Custom Function dependency rules (FileMaker Pro Advanced)
When you copy or import a custom function into a file, FileMaker Pro attempts to resolve any
dependencies the function may contain. The following dependency rules apply under different
conditions:
• If function_a has a dependency on function_b, yet only function_a is copied or imported into
a target file that contains a function_b, function_a calls function_b located in the target file,
which may cause unexpected results.
• If function_a has a dependency on function_b, yet only function_a is copied or imported into
a target file, function_a appears enclosed in comment characters (/*<function_definition>*/)
in the Manage Custom Functions dialog box, indicating the new function is invalid in the
target file.
• If function_a has a dependency on function_b, and both function_a and function_b are
copied or imported into a target file, function_a will operate as expected.
• If function_a has a dependency on function_b, and both functions are copied or imported
into a target file that contains an existing function_b, the copied function_b is renamed
function_b N. FileMaker
Pro updates function_a to call function_b N and function_a
operates as expected.
• If function_a has a dependency on function_b, and both functions are copied or imported
into a target file that contains an existing function_a and function_b, the copied functions are
renamed function_a N and function_b M. FileMaker
Pro updates function_a N to call
function_b M and function_a N operates as function_a in the original file.