Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata
  • Scripts: are named using a prefix which corresponds to the functional relevance to which they belong.

    Sidebar SelectRow Customer List

    good

    Select Customer in Portal

    bad

  • Scripts: Parameters in script names are identified by parentheses and separated with the semicolon. This follows FileMaker's default convention.

    Script Name ( with ; parameters )

    good

    Script Name ( with , parameter )

    bad

When passing multiple parameters into a script, it is suggested you use the Custom Functions » Script Parameter Interface functions from this site.

FileMaker Client vs. FileMaker Go

Note that the use of spaces and parentheses is not advised for scripts used within the Web or Mobile deployment of a solution.
(e.g. FMP7Script://192.168.10.0/FileMakerFile.fp7?script=ScriptName&param=SomeValue&$variableName=10)
More information about the URL Protocol Specification.
You can address this by using a distinct deployment strategy

Easier script filtering

As a solution grows in scope and complexity, it's advantageous to be able to use FileMaker's script filtering within the list of scripts. See the best practices for Suggested script naming prefixes

  • No labels

7 Comments

Hide/Show Comments

  1. Anonymous

    Having mixed thoughts about the comma separated parameters in script names.

    I see the reasoning, but

    1. Some scripts are used to act as functions

    2. In any area where there might be confusing they are always going to be prefixed by a 'Perform Script' 

    Is there really any scope for confusion, and why differentiate from custom and internal functions?

    Tim Anderson

    1. Arnold Kegebein

      Actual, I agree. FileMaker uses semicolon (;) as the separator character, not only for function parameters, but also to separate code elements (Let). Let us follow this ground rule in script names as well.

      The argument, making a distinction between script names and function names, has less weight. The context already makes it clear, whether the name belongs to a function or a script.

  2. Anonymous

    Could we also apply the tilde prefix for scripts that are only called by other scripts as suggested for custom functions?

  3. Anonymous

    Thanks for changing this to the semi-colon; I was about to make a point and now I don't have to!

    Nick Chapin

  4. Anonymous

    Perhaps I'm misreading, but it looks like the text suggests the use of a comma as the separator, but the example shows using the semicolon as the appropriate use.  I think one of those needs to be corrected!  :)

    1. Matt Petrowsky

      Fixed and references to the Custom Functions » Script Parameter Interface functions was added.

  5. Anonymous

    the #AssignScriptParameters does not work with the suggested Script Name ( with ; parameters )

    as the delimiter is set to comma. also "with" is not very clear. 

    maybe the example should be something similar to

    Script Name ( requiredparametername , requiredparametername ,

    Unknown macro: { optionalparametername , optionalparametername }

    )

    and note how to pass parameters using # ( "parameter1" ; $variableValue ) & # ( "parameter2" ; "Literal string value" )