TestStand 2016 SP1 reports a "File specified not found" error in a Property Loader step during the sequence analysis.
We use the expression browser to define a FileGlobals variable (path) in the Source Location for the Source Settings. There are no syntax errors reported and wrapping it with the "#NoValidation" function does not disable the error. The loader step works nicely for a path defined in the sequence at run-time.
The variable is defined at run time, so the TestStand analysis tool throws the error:
"Property loader source should be proper....does not exist. Modify the settings to provide the path of an existing file"
The error flagged in the loader step itself is:
"Errors:
SourceNameErrors
Setups: File specified not found
Process: File specified not found"
because there is not yet a file defined in the variable.
Our workaround is to have the name of an existing dummy file as the default in the path variable.
How can we switch off this analysis error for Source Location variables defined at run time?
