Teststand schema

[ADL]

We are introducing a number of new fields and tables to the SQL Generic schema. Actually implementing the changes we do not an issue with. Where we are having problems, is that the data gets transferred to Logging.xxx, prior to the data being inserted into the database.
How do we add data types to Logging.xxx without having to modify all the calling sequences and subsequences. We really want to make the modification in one place, so the data is automatically inserted every time the database.seq gets called.
Any help on the "correct" method to undertake this function would be appreciated.

A

[ADL]

I wanted to add a bit more information about this problem.
The custom data type "UUT" is stored within the custom data type tab of the sequentialmodel.seq, and this is effectively the information that we want to modify.
We want to add a number of UUT parameters that are specific for CUSTOMER X. These parameters are not step based but UUT base.
We wanted to change the data type in one place and let that propogate through to where its needed for example in database.seq, but unfortunatley it requires all the files that call the data type to be resaved. I believe we are doing something wrong, and would appreciate any help on this matter to add to the UUT parameters that get stored in the database, with the correct method from a architectural perspective.

A

[Scott_Richardson]

ADL -
The "UUT" custom data type is used by the process models to share information about the UUT under test. This data type is defined in the process model sequences. This version of the type default to the version specified by the TestStand engine when we release. If you want to add things to it, you can. You will need to add your new properties to the type, up the version of that type, which will remove the "modified" flag. All of your sequences that use an instance of this type will have the new property. This includes the database logging mechanism.

The only issue that you will have to deal with is when you upgrade to a new version of TestStand, you will have to make sure that you edit the new UUT type in the new version of TestStand to match the older one so you do not loose your changes, or you can up the version of your copy above the one that the new TestStand ships with and that will replace the copy in the new version of TestStand.

You should only do this with custom data types, not NI step types or our standard data types.