The file I inherited includes several scripts that feature a single “if” script step: If get script parameter = “x” Do stuff Do stuff Do stuff End if Exit For long scrips, this needlessly indents the script by one level. My thought process is: If get script parameter = “x” #Continue Else …

This is called the Early return pattern . In your example, I would use not equals (either <> or ≠ ) instead of equals ( = ) and avoid the Else If statement to make it even cleaner: If Get(ScriptParameter) ≠ "x" Exit Script End If # if we get here, everything is OK Do Stuff Do Stuff ... See …

Thank you, @xochi I appreciate your info and links. The Medium article was very helpful.

I wanna add to @xochi 's excellent answer. One common pattern in FM scripts that I see frequently, and use personally is a "single-pass loop" for early exits and error trapping. This pattern allows you to add multiple guard clauses or exit conditions, but still centralize the actual Exit Script step…

“If” Script Step

Questions

Bobino January 15, 2024, 2:06am 5

Thanks @jwilling for the shoutout. For anyone interested, the same demo file was used as the core material for a presentation I mentioned in this other thread: Error trapping advice - #7 by Bobino

Topic		Replies	Views
Scripting: If Statements and Exit Script Lounge (Discussions) scripting , optimization	8	505	June 8, 2021
Scripting an AND conditional...Single Line "If" or Nested "If"s? Lounge (Discussions)	10	658	May 10, 2021
Using ‘Exit Script ()’ at the end of a script - do or don’t? Lounge (Discussions) scripting , style	18	760	January 23, 2020
FileMaker Fail Early	15	610	December 25, 2024
Scripts That Call Themselves Lounge (Discussions) scripting	4	109	December 7, 2024

“If” Script Step

Related topics