Failed to run the 'Print Command Script' action. Details: No records found.
I have a pre-existing BarTender template I'm working with. Previously, it had one database connection, that to a CSV file. This file looks like the following:
%BTW% /AF=F:\bartender\CompanyName\RAW.btw /D="%Trigger File Name%" /PRN="PrinterName" /C=1 /R=3 /P
%END%
item}lot}qty}xprog
1207}50871}300.00000}RAW
1207}50881}200.00000}RAW
I need to add a new field to this template and decided to add a SQL Server database connection to do so. The DB connection works fine, and in Designer I'm able to spit off prints against a 'test' CSV file no problem. The problem comes when I push it out for Integration to handle in production. I get the error stated in the title, of no records found.
The SQL connection joins on the CSV file connection to know which record to pull from the SQL database. I can see this join is working because of 1) the successful test prints, and 2) I can see the record in Record Browser in Database Setup.
My suspicion is that somehow the SQL connection is trying to complete its query before the CSV side has had a chance to pull the file data. However, I see no explicit way to control that sort of behavior, and no proof that's the case.
I've tried changing the user credentials on the integration job to use an admin account (mine), to no avail. I've tried changing the SQL database connection permissions to a SQL user, to avoid any windows integration resolvement issues. The Print Command Script action has the following settings:
The test CSV database file has the following content:
item}lot}qty}xprog
1207}50871}300.00000}RAW
There is only the one action, of Print Command Script.
Any ideas what I'm doing wrong?
-
pthane
★ BarTender Hero ★
It does sound like permissions type issues if it works in Designer.
Quick question, can you change the CSV output file without too much effort?
If you could you could remove the Commander Script commands from the top of the trigger and add the variable elements in as part if the data string, such as:
item}lot}qty}xprog}printer}label}quantity
1207}50871}300.00000}RAW}Zebra1}ProductLabel}5When you connect the Integration to the label you would then be able to configure those details as variables linked to the field in the trigger file and also do the same for the database lookup (lot or item I am guessing)
0
Iniciar sesión para dejar un comentario.
Comentarios
1 comentario