|Download Help (Windows Only)|
Use the Property Loader step to dynamically load property and variable values from a property loader source (a file or database containing data for your property objects). The new Property Loader features more intuitive user interfaces, logs more details in the result list, supports the use of alias names, and allows you to preview your imported data before you finalize the import operation.
The Property Loader also features plugins to support importing and exporting data to and from custom formats. You can import and export to and from an Excel workbook (.xlsx) file even on machines that do not have Microsoft Excel installed.
You can apply the values you load to the sequence executing in the current thread. For example, you can develop a sequence that tests two different models of cellular phone, where each model requires unique limit values for each step. To specify limit values, include a Property Loader step in the Setup step group of the sequence to initialize the property and variable values of the sequence.
You can also load values for properties into sequences so that all subsequent invocations of the sequences in the file use the dynamically loaded property values. For example, include a Property Loader step in a ProcessSetup model callback sequence the execution calls once so the execution can call the client sequence file multiple times with the dynamically loaded property values.
You can load values from multiple sources in a single Property Loader step. For example, when testing a specific model of cellular phone, you can import data from a property loader source that contains limits for a generic model of cellular phone and also import data from a property loader source that contains updated limits for the specific model of cellular phone. By doing so, the Property Loader will import all limits defined for the generic model and then import limit values defined for the specific model, thereby overwriting the limit values for the generic model.
|Note In TestStand 2016 and later, the Legacy Property Loader step is no longer listed in the default type palettes installed by TestStand. If you open a sequence file with a legacy step, the legacy step type will appear in the insert step menu, and you can still execute sequences that contain the legacy Property Loader steps. The Legacy Import/Export Properties tool in the Tools menu is not installed by default. You can manually add the legacy tool by importing the <TestStand> \Components\StepTypes\Database\LegacyImportExportTool.ini file in the Tools menu. See the Importing and Exporting with a Legacy Source topic for more information.|