- Custom functions: are named in the familiar FileMaker format of TitleCamelCase. It is assumed that distinguishing internal from developer-based custom functions will be evident based on access to the custom function list - so no distinct naming differentiation is used.
ObjectID
good
object.id
bad
- Custom functions: which are private in nature, meaning they're functions reserved for use by other Custom Functions, those not called directly from within calculation code, are prefixed with the tilde ~.
~PrivateCustomFunction
good
_Private_Custom_Function
bad