FM14 treats local variables as global variables (2 Comments)

Issue report by Michael Rhodes

Product

FileMaker Pro

Version

14

Operating system version

Windows Server 2012

Description of the issue

Local variables declared in a Let statement (and possibly also Set Variable step) are not flushed after the script is executed. They won't show up in the Data Viewer unless you manually add the local variable as a statement to evaluate. However, the variable's value is definitely evaluated by any subsequent scripts. As you might imagine, this is a critical bug, as often a local variable is only declared under defined conditions, and due to this bug, scripts now see values assigned to that local variable once declared in a prior run script.

Steps to reproduce the problem

Create a script that declares a local variable (may require declare by Let command). Run it. Open Data Viewer and add that variable for analysis.

Expected result

Local variable should be null after script is executed.

Actual result

You will see the local variable which should be null after script has run retain it's value.

Configuration information

Using 14 Advanced.

Workaround

Add script steps to set all local variables to null at beginning of each script.