ReportView Control not populating

[awooster]

I'm using LabVIEW 2016 to develop a simple user interface for executing test sequences created in TestStand 2016, and I'd like to use the ReportView Control in this user interface.  Unfortunately, the control remains blank when I run test sequences through the user interface.

In my debugging I tried executing the "Connecting UI Controls Example" in TestStand, and the ReportView Control in this example also remains blank when executing the example test sequence.

Am I overlooking a setting somewhere in TestStand that is preventing this control from populating?  The "Report" output is enabled in the TestStand Results Processing settings, for what it's worth.

Thanks,

Andrew 

[Norbert_B]

---

@awooster wrote:

[...]  The "Report" output is enabled in the TestStand Results Processing settings, for what it's worth.

Thanks,

Andrew 

---

And you DO get a report file?

Which process model are you using?

[awooster]

---

---

And you DO get a report file?

---

Good question, looks like you're on to something.  When I execute the sequence file in the development environment, a report is generated.  When I execute it via the user interface, however, a report is not generated (i.e. there's nothing to display in the ReportView Control).  I'm using the Sequential process model. 

[Norbert_B]

Does your custom UI modify configuration settings of TS?

How does the default UI examples work on this?

[awooster]

Just updating this thread..

I was using the "Basic User Interface.lvproj" from the "Examples" workspace in TestStand, and I was trying to add the ReportView control to this example.

What I've done instead, and had success with, is use the full-featured operator UI located in C:\Users\Public\Documents\National Instruments\TestStand 2016 (32-bit)\UserInterfaces\Full-Featured\LabVIEW.

This example already has the ReportView control built into it, and everything functions as I want it to.  I believe the issue I was running into on the basic user interface example was that the sequence file wouldn't actually complete its cleanup (and the report wouldn't generate).