Variant data in type specification structure

[szewczak]

Hello all,

In the attached VI snippet I have a Type Specification Structure (TSS) that I want to be able to include a case for what to do when wired Variant data as a separate case from 'unknown, use last diagram' data.

As per Manual:

Type Specialization Structure
Has one or more subdiagrams, exactly one of which LabVIEW compiles and executes, depending on the order and the compilation result of the subdiagram.
LabVIEW declines subdiagrams in order if they have syntax errors.

My problem is caused by all 'unknown datatype' being typecast to the variant case, and never reaching the 'unknown datatype' subdiagram.

Any suggestions on how to get the following behavior out of a TSS?

1. If Numeric element is wired, run this subdiagram
2. If Boolean element is wired, run this subdiagram
3. if Variant element is wired, run this subdiagram
4. in all other cases run this subdiagram.

[crossrulz · Accepted solution]

One of the new toys included in LabVIEW 2018 is the Assert Type function.  It is hiding in the Comparison->Assert Type palette.  What this function does is break a diagram when the two inputs do not match data types.  So if the input is, for example, a string, it will break the Variant case and so the next case will be chosen.