Write UUT Serial Number scanned at beginning of test sequence to a text file

[James_D22]

Is there a way to get the Serial Number string / value that every default test stand sequence scans and store it to a text file? What variable / parameter is that scanned value even stored in? 

I tried using a Call Executable function like in the screenshot attached. But whenever I go to that output file, it is blank. Am I calling the wrong parameter? 

[Oli_Wachno]

Think you are missing the redirection of the echo command to the file

echo somtehing > test.txt

[James_D22]

Do you happen to know if that parameter of "Runstate.Root.Locals.UUT.SerialNumber" is the correct parameter to pull this data from? I fixed the echo command by adding > and I even tried >> to just have it overwrite whatever is in the test.txt file. But nothing is still written to that file. 

[Oli_Wachno]

Does the Write to file operation work with a constant string?

RunState.Root.Locals.UUT.SerialNumber is correct, yet it is only existing when the process model is run

[James_D22]

I tried to just put in "hello" as a string in that command and nothing got written to the test.txt file.

[Oli_Wachno]

I am confirming this behaviour ☹️

I could get a file created when redirecting STDOUT to the file. Yet the file seems to get overwritten each time, so no appending

[James_D22]

This attached picture allowed me to print the string "test" into the test.txt file I had on my desktop. 

Now just need to get this to work on actually pulling the UUT serial number during runtime to get that recorded into a .txt file.

[Oli_Wachno]

I had tried the \\ as well but failed, seems I still made another mistake

Suggesting another solution: have you considered using a data stream step type to write in a kind of nicely formatted csv File?

[James_D22]

I will have to try this. My concern is that I cannot pull the UUT serial number into any file (whether .txt like I am attempting now, or via a .csv data stream) as I cannot find the Runtime variable that it gets stored to. But will need to at least try to see what I get.