What Are Best Practices for Custom Data Types in TestStand?

Updated Oct 30, 2024

Reported In

Software

  • TestStand

Issue Details

What are the best practices for using custom data types in TestStand to ensure that changes are propagated to all sequence files?

Solution

For a full discussion of how to properly implement Custom Data Types, refer to NI TestStand Type Management Best Practices.

 

Additional Information

A TestStand application loads files that contain types in the order shown above in the list of files used to store types.  When a file is loaded, all the types defined in the document are loaded into memory as well. Each type is uniquely identified by name and version number. 

The engine selects the version of the type to use and updates all instances of the type to match the one the engine selected ​because the TestStand Engine can only have one version of a type in memory at a time,.  By default, types are configured so that the engine selects the type with the highest version number.

Related Links

Type Properties Dialog Box

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.