Print Priority & Jumbled Print Jobs フォローする

0
Avatar
Legacy Poster

Hello all, 

 

Currently commander is picking up our files as they are dropped to the directory.  It spools each label as an individual print job.  As such, it is printing the labels intermingled.   Can I set Commander to finish one file's print jobs before spooling to the next?

7 コメント

0
Avatar
Ian Cummings
モデレータ
コメントアクション Permalink

Unfortunately Commander doesn't have such functionality.  Either adjust your application creating the trigger so that it appends records to a file in a temp folder, or memory string in memory, and then only when a print is wanted does the file get saved to the scan directory.

0
Avatar
Legacy Poster
コメントアクション Permalink

How then do you handle a warehouse setting where you may have multiple print jobs running at any given time to the same printer.  The application, (SAP), is already spooling a single file to commander.  however, through the BTXML it reads each instance of the XML label script and sends it to the printer as an individual print job.  As such, it is sending labels intermixed.  

 

There has got to be a way to hold the job for that printer until the previous job prints.  We can't be the first company in the world with this issue for Commander. 

0
Avatar
Domingo Rodriguez
モデレータ
コメントアクション Permalink

Does each XML Script trigger file contain multiple print jobs, or just a single one?

 

It should be noted as well that if Commander is spawning multiple BarTender processes print job order cannot be guaranteed. You would instead  configure the command handler (go to Menu "Detection > BarTender Command Handler") to just start 1 BarTender process. This will guarantee that each trigger file is being processed in order by time stamp.

0
Avatar
Legacy Poster
コメントアクション Permalink

Sorry for the delayed response. 

 

Each BTXML file has multiple print commands.  One for each label.  If someone can provide a BTXML format where I can spool the entire print job in one print command but define data for 400 labels within the command, that would be great.  

 

We are seriously considering scrapping Bartender all together over this one issue.  We ship retail and each UCC128 label is unique to the customer and carton that it is generated for.  It is not uncommon for us to ship thousands of cartons on a single order.  Given the size of the facility and volume, the printer banks along the shipping lines are shared and we are often running multiple different shipments at one time.  With that said, UCC128 labels for Walmart are getting mixed with Walgreens or Target etc...

 

it is a huge logistical nightmare and I really need a solution to this.  Like I said before, we can't be the only ones doing this with Bartender.  if we are, Bartender is the wrong software package for us. 

0
Avatar
Ian Cummings
モデレータ
コメントアクション Permalink

In this example of BTXML script, from the BarTender Help system, you'll see two records for a single print job to a specific printer.  It could just as easily be for 400 records.  This will produce a single print job, with printed labels remaining in proper record order.

 

<?xml version="1.0" encoding="utf-8"?> 
<XMLScript Version="2.0">
<Command Name="Job1">
<Print> 
<Format>c:\BarTender\Document1.btw</Format>
<RecordSet Name="Text File 1" Type="btTextFile">
<Delimitation>btDelimQuoteAndComma</Delimitation>
<UseFieldNamesFromFirstRecord>true</UseFieldNamesFromFirstRecord>
<TextData> 
<![CDATA[ 
"FirstName","LastName","City","Zip Code" 
"Adam","Jones","Bellevue","98008", 
"John","Smith","Kirkland","98293" 
]]> 
</TextData> 
</RecordSet> 
</Print> 
</Command> 
</XMLScript> 

Does this not solve your problem?

0
Avatar
Legacy Poster
コメントアクション Permalink

I did see this solution in the forums.  I am not very keen on the idea and it will require the redevelopment of about 150 labels as they are currently all set to run from named data sources with the XML tagging, but I will test this.  I appreciate the response.  

0
Avatar
Ian Cummings
モデレータ
コメントアクション Permalink

Changing the value of data sources directly is only suitable for a per print job basis.  Changing the data source, through record data, is the way to go about it per X number of labels in a single print job.  This has always been the case using XML or any other method of automation.

サインインしてコメントを残してください。