Bartender integration Command line error
Hello,
We are in the process of migrating to Bartender 2022 r8. I set up the integration from the old Bartender Commander.
I made an integration based on Bartender Command line.
My command is: /PRN="ZEBRAZT420_1RTD" /P @"%Trigger File Name%".
I get the following error message:
The 'BarTender Command Line' action was unable to execute its BarTender command line because it is invalid. Retry again after verifying that the command line is using the correct syntax and that all options are supported. Details: The BarTender command line '/PRN="ZEBRAZT420_1RTD" /P @"\\sens.local\dfs-data\Userapps\CommonSens\bartender\rptBartenderPalletLabel2\516508.bak"' cannot execute because the parameter '@"\\ sens.local\dfs-data\Userapps\CommonSens\bartender\rptBartenderPalletLabel2\516508.bak"' is unsupported. The parameter may be misspelled. Correcting the parameter or removing it from the command will allow the command to execute.
Anyone have an idea
-
I think it should be /D="%Trigger File Name%" not @
0 -
When I change the command to /D="%Trigger File Name%" I get the follow message:
The 'BarTender Command Line' action was unable to execute its BarTender command line because it is invalid. Retry again after verifying that the command line is using the correct syntax and that all options are supported. Details: The BarTender command line '/PRN="ZEBRAZT420_1RTD" /P /D="\\sens.local\dfs-data\Userapps\CommonSens\bartender\rptBartenderPalletLabel2\516508.bak"' cannot execute because at least one open BarTender document argument must be specified on the command line (/F or /AF). Specifying a BarTender document to print will restore all the command to execute.
My commandline is like this: /PRN="ZEBRAZT420_1RTD" /P /D="%Trigger File Name%"
0 -
Sorry completely missed you had no label format name in the command string!
You will need to include this with the appropriate /F= or /AF= parameter. Alternatively, as long as you are using BarTender 2019 or later, if you could add the printer name and label format as a data field in your trigger file could configure Integration Builder to look for these parameters in there and so all you would in the trigger file would be the data including these details
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires