How to recreate TLV Datastore Tables

TLV stands for TierListView. You can refer other knowledge base articles that show how to use TIER® MultiCommands like .SaveSelectedRows and .SaveAllRows to create a “TLV” table in the database and store the data selected there. But what happens if you need to make a change to your TierListView and add a new column? Here’s another tip for those of you who save data to “TLV” tables. TLV tables mimic the columns in the TierListView, with the exception of an extra field at the beginning (TLV_DocID). If an additional column is added to the listview, when a user attempts to run a MultiCommand like .SaveSelectedRows, the following error message may appear: (See attachment for screen shots)The error message displays the name of the new column that was added to the listview which doesn’t yet exist in the TLV data table. For example, the column named MaritalStatus was added to an existing listview, TLV_StaffList, but is not in the TLV_StaffList table yet.To eliminate error messages like the one above, the columns in the TLV table must match the columns in the TierListView. This can be done in two different ways:• Manually add the column to the table in the databasealter table tlv_stafflist add MaritalStatus varchar(50) NULL• Drop the TLV table in the database and let TIER® recreate the entire TLV table the next time someone clicks the button that performs the .SaveSelectedRows command.   drop table tlv_stafflistEither way you choose, it’s a good idea to manipulate the columns in both the listview and table after hours so as to not affect the work of your users.( See attachments for entire TIDBIT)