Cmmander Task To New Integration Issue S’abonner

0
Avatar
Legacy Poster

I just installed a trial of version 2016 R2.  We're currently using 10.1 SR4 (Automation) on a different system.  I ran the "Import Commander Task List" on our active Task to see how it works for the new version.  It runs a file detection and then a print command script.  After trying the "Test Integration", I receive this message.

 

Action 'Print Command Script' 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: Input string was not in a correct format.

 

I don't know where it's going wrong. The %EventData% is showing the same text that's inside the TXT file that's dropped off.  The text inside the file looks like this:

 

%BTW% /AF="C:\BarTender-Docs\Templates\test-label.btw" /D=%Trigger File Name% /PRN="ZebraZT410" /R=3 /P /DD /C=2%END%Data Field 1~Data Field 2~Data Field 3~Data Field 4~Data Field 5~Data Field 6~Data Field 7~Data Field 8

 

(~ is a custom delimiter)

 

I've been trying to read the new manual online, and I'm really not getting anywhere with it.  Does anyone have any insight for us?  Maybe a different document that better explains the command line scripting?

 

Much Appreciated!

6 commentaires

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

One would expect the print command script to look like the following:

 

%BTW% /AF="C:\BarTender-Docs\Templates\test-label.btw" /D="%Trigger File Name%" /PRN="ZebraZT410" /R=3 /P /DD /C=2

%END%

Data Field 1~Data Field 2~Data Field 3~Data Field 4~Data Field 5~Data Field 6~Data Field 7~Data Field 8

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

There are two differences between my text and yours.  First, I was missing the quotes around %Trigger File Name%, which didn't matter either way.  The second difference was how you typed it, with returns after each of those lines.  Once I set it up that way in the TXT file, it ran through without any problems.  Looks like I'll have to make sure there is a return before %END% and also before the data fields.

 

Thank you for your help!  You truly are a Ninja!  :ph34r: 

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Can anything else cause this error.   I am using Intergration Builder set for File Detection and a Print Command Action

Here is my EventData:

 

%BTW% /AF="\\WIN-2012R2PH\SyteLine\Bartender\SytelineShippingLabel" /PRN="Brother HL-L2340D series Printer" /P /D="<Trigger File Name>" /C=1/R=3
%END%
1|||||||||FA-10000|Bicycle,Model-30,26"x|EA|3.00000000||||||             12|Demo|MAIN|FIN-1|     19|0|H.H. Squash|
 
The delimiter is |
 
 Thanks,
Ed
 
 

 

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Ok.  I figured out my issue. There needed to be a space between the /C=1 and /R=3.  Yikes!  This is a bug created by Infor Syteline vb script that produces the text file.

 

Ed

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Good to see you have got it working.  As a quick FYI, in the next few days we'll be releasing BT 2016 R3 which I highly recommend you getting.  Keep an eye out on this page: http://www.seagullscientific.com/support/service-releases-legacy-versions/2016/

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

R3 has now been released.

Vous devez vous connecter pour laisser un commentaire.