Property Loader called from within Model help

[AndyTT]

Hi All,

I have a problem with loading in test limits and traceability information into my sequence.

I have my property loader in the ProcessSetup Callback within the SequentialModel.

I can successfully setup the property loader to load limits into my MainSequence and can also setup my property loader to load traceability information into the Model.

The problem I have is I cant do them both from within the same file. I would like to have one limits file that contains all the data needed for the sequence file and some traceability information.

I am using Teststand 2016 SP1.

Does anyone have any ideas what I could try or if this is even possible?

Thanks

[Shashidhar · Accepted solution]

I have attached your example after modifying it. I have merged two csv files into one file where it has two <PropertyGroup> section.

For the specified example, I believe there are two ways of achieving your request. In the Process Setup sequence, I have created two property loader step and each uses a different way to achieve the same result. To test, skip one of the property loader step and execute your sequence file.

The following explains what are the two ways of achieving your result.

Solution 1: Using 'Load Source Prototype'
Disable 'Import All Properties From Source' in the 'Step Settings' tab.
In the 'Target File and Source Settings' tab, in the property selector, next to the search button, use 'Load Prototype' and specify the source as the CSV file which contains two <PropertyGroup> section.
Launch 'Property Selector Diaolg' using the last button (next to clear button) in the property selector. The dialog lists all the <PropertyGroup> existing in the CSV file. You can disable the property group which you do not want to use for import.

Now, the only challenge here is that, since 'Import All Properties From Source' is disabled, whenever you modify the csv file to include other properties to import, you need to do the above mentioned steps of loading the source prototype and disabling the PropertyGroup which should not be imported.

Solution 2: Using target sequence settings
This uses the fact that the sequence to which data should be imported is different for the model and the client file.
Enable 'Import All Properties From Source' in the 'Step Settings' tab.
Change the 'Import Values To' in the 'Step Settings' tab with the sequence name to which the data should be imported. This will make sure that all the data present in the CSV file which does not corresponds to the specified sequence is ignored.

-Shashidhar

[AndyTT]

Thank You Shashidhar,

This works great.

[AndyTT]

Hi,

I have been playing around with the property loader and come across a situation that I cant seem to solve. Based on the previous problem above,  I have two sets of data that I want to import into my sequences. Both sets of data are within the same file.

This works when the tests are within MainSequence but when the tests are within sub sequences it falls down.

Is there a way to configure the property loader to load limits into sub sequences?

I can get this to work but I have to remove one group from the source which means I would have to create two files to contain my limits/data. Ideally I want everything contained within a single file.

Thanks

[Shashidhar]

In PreUUT >> Import data Non Standard step, it was configured to import all the properties from the csv file to the client sequence file (which is Dummy.seq in the example). Importing all the properties, will also try to import a variable into 'Test UUTs' sequence, which does not exist in the client sequence file. Hence, it will error out mentioning that sequence does not exist.

I have updated the property loader step in the sequence file as follows:

- Used load prototype in the property selector and loaded all the information present in 'PropertyLoaderSource2.csv'

- Used property selector dialog and disabled the group 'Settings Group' which contains data to import to Test UUTs sequence

Executing the sequence file after making those changes works properly. I have attached the updated sequence file.

-Shashidhar

[AndyTT]

Hello Shashidhar,

Thank you for your reply. Unfortunately I was not able to open the attached file.

Error Code: -17001

Source: TSAPI

I am using Teststand 2016 SP1 perhaps its saved in a newer version?

Thanks