Back to Blog
Stageplotpro printing issues5/16/2023 ![]() Empty or unlisted named data sources may simply use sample data during print time.ĪctiveX and. If you are using named data sources, ensure that all are listed.If a label is connected to a CSV file, for example, you cannot give it an XML database in an integration. Ensure the trigger file database type matches the label's database.Check the database connection (for database integrations) to ensure there are no errors connecting.Check the trigger file (for most integrations) to ensure it has data and the correct data. ![]() Check the integration logs in the Administration Console or in Integration Builder for errors.Not an exhaustive list, but here are some suggestions when working with automations to get you started: This makes troubleshooting this step in the process a bit more difficult as the data could come from a myriad of sources. When an automation such as an integration come into play, the data likely originates outside the label. This can usually, but not always, be done by simply opening BarTender's Database Connection Setup dialog. You want to make sure that BarTender is able to connect to whatever database is in use and that the database contains the correct information. You primarily see these when printing from Designer, Print Station, and Print Portal, though they may also show up in integrations and automations as well. While data entry forms are a bit harder to troubleshoot as it could easily boil down to user input error, database connections are easier to control. When something goes wrong at this step, you want to ensure that BarTender is able to connect to the data source and that it contains the correct information. BarTender can retrieve data for printing through a wide variety of means including data entry forms, database connections, and data contained within a trigger file. This is an important step in the printing process, and one that is often prone to breaking.
0 Comments
Read More
Leave a Reply. |