Every CSV file uses only one label but different numbers of entrys
Hello,
The Integration Builder print labels with data from a CSV file. The label layout is identical for all data records in the CSV file, only the data is different.
If we use Bartender with the csv file directly, all labels are print out quickly.
Our actually Integration Builder configurations seems to fetch and print each label individually. Instead of a print job with multiple pages, all individual print jobs are then triggered. We believe that the label will be reopened each time instead of using the same label for each line. For a csv with several 100 entries, this process takes extremely long (at least 2 seconds per label).
How can we set this up in the integration builder so that it works similarly to the direct Bartender call. So opening the btw file once and quickly printing all lines with the opened layout?
Here is our CSV File:
Every CSV file get an individually Label. This is only an example.
Current structure of the Integration Builder:
Best,
Andre
-
Yes, the Integration has been configured to process each line individually. The label format will also need to open each time as the label format is declared as a variable, if it were fixed then this may speed the process up.
0 -
Hello Peter,
thanks for the reply.
How do I fix this?
The label format is in the csv. How can I set it for the whole CSV?
0 -
Via the Dokument entry box shown in your screenshot above. If you browse and select your 252029......dynamish,btw then give it a test and see if that improves performance
0 -
That doesn´t impoves the perfomance. It takes the same 2 seconds to send the data to the print scheduler.
What else can I do? I get the newest printer drivers from seagull and change the font to the printer standard font.
Nothing works for a better performance.0 -
If your file name is always the same you could try a couple of different way:
- link the label to the CSV in a different folder to where it is normally created.
- Set your Integration to Move the detected file into the folder above replace any existing file
- Configure a Print Document only Action in the Integration to print the label when the file is detected
(not sure if you may need a Wait command to allow for the file to be created/moved)
Or
- Link the label to copy of your CSV that has a different File extension (ie DAT not TXT) to the trigger file being created
- Configure the Integration to rename the file to this new extension replacing any existing
- Setup up a Print Document action to print the label which should then use the renamed file as the database as that is the file name/type it is linked to
0 -
Hello Peter,
thanks for that. We are testing it. Sounds good.
0 -
Hello Peter,
thanks for this. It works great!
0
Iniciar sesión para dejar un comentario.
Comentarios
7 comentarios