With Labeler v7, we now have the ability to use a direct connection to MSSQL databases, rather than going through the ODBC connection. When working with the prebuilt Asset labels, we should use this new connection.
First, go to Labels, click on Asset Tags, then click Edit:
Click Yes when prompted to overwrite your current label. This will open the label in Labeler v7.
On the Data tab, if it is not showing a preview of the vLabelerAsset_AssetTag table, click Remove Connection. To re-add it, click MSSQL. Fill in the Data Source - MSSQL Server information for your server, username AssetReader, password ReadOnly@1ReadOnly@1, and database WaspTrackAsset.*
Click Test Connection, which should respond that it "Completed successfully!", then click Apply. If it prompts you for Object to Column Mappings, click Cancel. On the drop down list, set it to vLabelerAsset_AssetTag. On the right hand Properties pane, it will list the columns. Click Select All at the bottom to allow all columns from that table to be used for label objects.
On the Design tab, on the Properties pane, select BarCode from the drop down list. Click on the Content tab, then click Database. Select asset_tag on the drop down list and click Done.
You can set the Placeholder back to 1234 to return the barcode object on the template to its original size.
On the dropdown list at the top of the Properties box, select Description, then follow the same instructions as above to set its Content Source to asset_description. Switch to the Print tab to verify that the label looks correct with your data. You can select a different label size with the Layout button, or reposition the label objects on the Design tab as needed.
Once the label is designed as you need, go to the File tab, click Save, then close Labeler. Click Save Changes in the Asset Tags window to commit the label to the database.
The other prebuilt labels can be reset the same way with the MSSQL connection. Please contact Wasp Support if you need assistance determining the correct table and columns to use for each.
*Enterprise only: If you are using multiple companies, each company database will have its own versions of the labels saved within it. For the Database line on the login information, specify the correct database, WaspTrackAsset_01, WaspTrackAsset_02, etc.