Commander And Query Prompts
I am evaluating Bartender for use in our organization and I am having an issue with Commander. I have a label configured with a database connection and a query prompt. Everything works fine in Bartender. I set up a Commander task to print my label and nothing happens. Here is my command:
With the recent release of BarTender 2016 we replaced Commander with the much more capable Integrations Platform. I suggest you download and install the latest Trial and test that instead. See the below white paper: http://www.seagullscientific.com/media/101724/bartender-integration-builder-201511.pdf0
Is there an example available using the Integration Platform and a Query Prompt? I have upgraded to the new version but I still cannot get it to work.0
What event type do you plan on using for the integration: file, web service etc? What format with the event content be in: CSV, params, JSON, XML etc?
Depending on what you answer above will I answer you accordingly.0
I am planning on using file intergation with a text file containing query prompts. Here is my command:%BTW% /AF=E:\JWL\SampleLabels\Label_QueryPrompt.btw /PRN="WPPUS_CHQ_MIS_Zebra105SL" /P /?OrderNo="322458"%END%My plan is for my ERP system to create text files containing the name of the label to print, the printer, the number of labels to print and a list of parameters for my query (there will be 5 or 6).0
I note that you're using what I assume to be a mapped drive letter reference "E:\" for loading the document file. It should be noted that these are user account specific, and by default your actions will run in the Windows System account which will not have the mapped drive reference. With this in mind it's usually better to make use of a UNC path instead. For example: \\ComputerName\ShareName0
I will update my reference to the label file.
Is my approach workable? I have fixed some syntax errors and I can get a basic test label to print.
I was also wondering if there is any way to change the database the label is referencing from the command line?0
Using print command script to open a label, specify a query, and to print is fairly standard stuff so I don't see a problem with it per se. Concerning switching the database; this can only be done if the document is connecting to a data file (text file), if instead this is a fixed database like Access/SQL Server, then no this is not possible.0