Remove Callback from TestStand Report

[pulidotech]

I have a number of callbacks in my TestStand sequence, e.g. ProcessModelPreStep, SequenceFilePostStep, etc.  

I can disable result recording for all the steps within the callback.  Is there a way to disable result recording for the callback itself?  I don't need my XML report to say anything about those callbacks.  

[~jiggawax~]

I would be very surprised if any of the callback steps are showing up on any of your reports.  Only steps from MainSequence and any of it's direct hierarchy will be passed back for result processing.

In any case you can go to the sequence properties of any sequence and check the Disable Result Recording for All Steps option on the General tab.

Hope this helps,

[pulidotech]

The callback steps are in my XML report.  They're just ignored by the stylesheet.  Attached is a screenshot of the report.

I happen to have a sequence that produces a fair amount of data and I'm just trying to reduce the file size.

I already disabled result recording for all steps, but I want to get rid of the callback itself from the report.

[~jiggawax~]

ProcessModelPreStep can only exist as an engine callback inside of a sequence file marked as Model.  Are you telling me that hello.seq is your process model?

I've written hundreds of plugins and I've never seen steps from a callback show up in the result list, especially in the MainSequence result list.  My guess is that somewhere in your MainSequence you are calling into hello.seq?  If so then they will show up in the report. 

find the step that is calling ProcessModelPreStep and disable result recording for that step.

If you want to PM me your entire xml file I can probably shed some more light on what's going on here.  My assumptions above are based on the snippet in your attachment.

Regards,

[~jiggawax~]

SOOOO..... I learned something interesting about the pre and post step engine callbacks.  They put stuff in your result collection.  I've never had to deal with them before or I just ignored them when they were there, which it looks like the xsl file is ignoring them.  This is true for all 3 levels of engine callbacks- SequenceFile, ProcessModel and Station.

Changing the sequence settings to disable result recording will help with size but you will still get the entries for every step, as you've noticed.  I cannot find any flags or anything to turn this off and there is nothing in the help that I can see that will turn these off.

You can modify the plugin to discard the data before it gets injected into the XML file.  Or you can purge your resultlist before mainsequence exits.  Either way will reduce the size of your XML.

This document states that if you disable the result recording you shouldn't see the results: https://www.ni.com/docs/en-US/bundle/teststand/page/subsequence-results.html

So in my mind this feels sorta like a bug?!?

[James_Grey]

I think the distinction of whether something is in your results is not based on whether it is a callback, but on whether it is executed beneath the call to mainsequence. So, I'd say this isn't a bug.

[~jiggawax~]

---

@James_Grey wrote:

I think the distinction of whether something is in your results is not based on whether it is a callback, but on whether it is executed beneath the call to mainsequence. So, I'd say this isn't a bug.

---

I'm only saying that it feels like a bug because it contradicts the documentation.  In the documentation is says that by disabling result recording for any of those callback sequences it won't put entries in the step results...at least that's how I read it.  Maybe it still puts the placeholder??? 

From the help: "When a step calls a subsequence or generates a call to a callback sequence, TestStand creates a special step result subproperty of the Step.Result.TS property to store the result of the subsequence unless the callback or sequence disables results."

[James_Grey]

The last phrase in that documentation is wrong for both explicit sequence calls and callbacks because while the results lists will be empty, the records of the calls will still be under Result.TS.

[~jiggawax~]

---

@James_Grey wrote:

The last phrase in that documentation is wrong for both explicit sequence calls and callbacks because while the results lists will be empty, the records of the calls will still be under Result.TS.

---

Good to know.  Thanks for the clarification.

[pulidotech]

I opened a support ticket on this subject and NI R&D is confirming the behavior and it doesn't look like there's a way to not record the callbacks in the report.  Hopefully, the documentation/webpage can be updated to make it clear what is/isn't in a report.