override sequence setting

[RolfO]

---

@richjoh wrote:

Thanks for the response, I noticed for a sequence, the sequence setting always overrides the steps regardless of the step(s) being set to Record Results Enabled "override sequence setting".

Just to be sure: Is the "Result Record Option" for the calling step set to Enabled? If the caller-step has set "Result Record Option" to "Disabled" there will be no log of results from the subsequence even if all steps in that subseqeunce is set to logging.

For me, with TestStand 2012, things work as i expect.
(I do not know anything about horizontal.xsl so the previous line is not valid about anything related to that file.)

[richjoh]

Yes, I concur.

Editing the Stylesheet, horizontal.xsl could be another way to resolve the issue. But didn't work for me.

[richjoh]

So RolfO,

Your solution works when "on-the-fly" reporting is disabled. Thanks to member ~jiggawax~, he hinted at disabling on-the-fly to make this work in another post, https://forums.ni.com/t5/NI-TestStand/RunState-Report-Append-function/td-p/3981536 . More than 1 way to do this but looks like on-the-fly reporting should be disabled.

[richjoh]

Turn out the easiest solution is to modify the horizontal.xsl file. No need to include sequence calls if your formatting is no indentation. Start by making a backup copy of the horizontal.xsl (javascript) file. Edit the file by changing "var gIndentationWidth = 40;" from 40 to 0. Save the file, done. 

Reports still kinda ugly since the Seq header is separate from the result tables.

TestStand Help instructions sent me changing "gIndentTables" and looking for a boolean setting from True to False... these instruction were either out dated or wrong.

[RolfO]

Good that you have a simpler solution which seems to solve your problem. 

And thanks for info about "on the fly reporting" and that my solution seems to work also.