跳至主內容

搜尋

搜尋

Print Command Script works from command line, not from Integration Builder

評論

4 條評論

  • Avatar
    Pim Zandbergen

    I notice my example Print Command Script above has lines 3 and 4 joined which is not the case.

    Here is how it really looks:

    line 1: %BTW% /AF="E:\somepath\somedocument.btw" /D="<Trigger File Name>" /PRN="\\server\printer" /DBTEXTHEADER=3 /R=3 /P 
    line 2: %END%
    line 3: "fieldname1","fieldname2"
    line 4: "fieldvalue1","fieldvalue2"
    line 5:

    0
  • Avatar
    Peter Thane

    I have never tried to use the fieldname1....fieldvalue1 route I always set the label up linked to a dummy text file with the correct number of data fields and then in my trigger file the equivalent of your line 3 would not be needed and the file would look something like this. As you can see I have added values for 2 additional fields but left the 3rd one empty. 

    %BTW% /AF="E:\somepath\somedocument.btw" /D="<Trigger File Name>" /PRN="\\server\printer" /DBTEXTHEADER=3 /R=3 /P 
    %END%
    "fieldvalue1","fieldvalue2",,"fieldvalue4"
    0
  • Avatar
    Pim Zandbergen

    Thanks Peter. But unfortunately I have no control over the format of the trigger file.

    This is how the ERP system creates it.

    The ERP system was designed to integrate with Bartender Commander.

    It did used to work there. I would expect Integration Builder to be fully backwards compatible.

    0
  • Avatar
    Peter Thane

    I have just created a simple label and file and tested it and am getting the same error message. Playing around with the file etc. I was able to get if to print my data but I was still getting the error too. 

    I would suggest you send a copy of your trigger files and label format to the Tech Support Team and ask for some assistance from them.

    Pete

    0

登入寫評論。