NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

ReportOptions in TS 4.0

All,

I am setting up the report setting using the callback sequences. I am using a method that works fine in TS 3.5 but when I imported it into TS 4.0 it comes up with an error as shown in the attached word file. Also attached is a simplified version of what I am doing and it returns the same error.

Has anyone else seen this error?

S
Download All
0 Kudos
Message 1 of 6
(3,582 Views)
Hi,
Have you got more than one sequence file you are importing into TestStand 4.0? TestStand reports a file named "ReportGen_html.seq", which is not attached. It does give "Error in call to expression function 'Evaluate'. The expression cannot be empty." I can't seem to find where this expression is, can you point me towards it?
Thanks,
0 Kudos
Message 2 of 6
(3,543 Views)
Hi Kabul,

The "ReportGen_html.seq" is actually part of the NI setup and it stored in "C:\Program Files\National Instruments\TestStand 4.0\Components\NI\Models\TestStandModels" so I don't edit it at all.

Has something changed in the Report Options callback seq between TS 3.5 and TS 4.0?

Regards, Simon
0 Kudos
Message 3 of 6
(3,538 Views)
Hi,
 
The problems is in your ReportOptions. You have Locals.ReportOptions.ResultFilterExpression as an empty string. You setup some properties in Locals.ReportOptions then overwite Paramaters.ReportOptions. Parameters.ReportOptions.ResultFilterExpression is set to the empty string. The Evalute() in the precondition doesn't like this it should have as default "True".
 
I tried a small example in TS3.5 setting  Locals.ReportOptions.ResultFilterExpression  as an empty string and it still generated the same error. So I dont think there is any difference between TS3.5 and TS4 in this respect.
 
Can you post your TS3.5 example.
 
Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 4 of 6
(3,519 Views)
Hi Ray,

Thanks for your reply. I tried that out and it works fine.

I went back and looked at the TS 3.5 code that I found to be working. When I looked at the ResultFilterExpression parameter, there was a hardcoded value there with a formula to give a true answer and this is why it was working.

Thanks again for your help.

Simon
0 Kudos
Message 5 of 6
(3,486 Views)
Simon,
 
Ok that explains that, glad you are working now.
 
Regards
Ray
Regards
Ray Farmer
0 Kudos
Message 6 of 6
(3,482 Views)