Use Database result filter to remove sequence calls

[SteveSmith]

I am using a DatabaseOptions callback in TestStand 4.0 to configure my Access test database. One of the things I'm attempting to do is modify the ResultFilterExpression to prevent the logging of SequenceCall type steps. I've used the following with no runtime problems but also no success:

Step.Result.Status != "Done" && Step.Result.Status != "Skipped" && Step.StepType != "SequenceCall"

I've also tried Step.StepType.Name != "SequenceCall" (ran but didn't help) and Logging.StepResult.TS.StepType != "SequenceCall"  (caused a runtime error).

I can't turn off the Record Results in Run Options because that blocks the subsequence results.

Anybody have a solution?

Thanks,

Steve S.

[hansf]

I'm not positive about this, but I think you can use Logging.StepResult.TS.StepType != "SequenceCall"

Hans

[SteveSmith]

Hi Hans,

I thought that would work too. And it might if you cofigure database options from the Configure menu. But when I used that in the callback (see above) it caused a runtime error. Thats why the other statements were converted from Logging.StepResult.XXX to Step.Result.XXX.

Thanks,

Steve S.

[Scott_Richardson]

Steve -

I added an expression step to the DatabaseOptions callback and it worked fine. Its expression is shown below:

Parameters.DatabaseOptions.ResultFilterExpression = "Logging.StepResult.TS.StepType != \"SequenceCall\""

[SteveSmith]

Scott,

Thanks - that works great! That should reduce my record size by close to 50%.

Can you explain the purpose of the backslashes around sequence call so I can use them properly with my other filter expressions?

Thanks,

Steve S.

[adamg]

Hi Steve,

The purpose of the backslash is to escape the double quotation mark. You are assigning the filter expression to some sort of string which is characterized by double quotation marks. If you want to use the double quotation mark inside your expression string (in this case around the term SequenceCall) you have to escape it by using the backslash.

[SteveSmith]

Hi Adam,

That makes sense and may explain some difficulty I've run into setting the connection path with the database callback.

Thanks,

Steve S.