Serialization Of Labels Checked Into Librarian
Hello, I'm using Bartender 10.1 and I'm having trouble serializing labels that are checked into the Librarian.
It appears that Bartender on my setup is having issues with saving the file back into the Librarian after each print job, because the serialization function works fine for every batch that I print. Meaning to say that if I send a print job for 20 serialized labels, they get serialized correctly. However, once the file is closed and re-opened, the last printed serial number is not remembered and serialization starts from 1 again.
I've tried to play around with user rights in the Security Center, but even assigning administrator privileges to the user could not resolve this issue.
Separately, I get an occasional error pop up window which states that a temporary image of the label could not be saved to a local location on my PC (see attachment).
Can someone please guide me through how to resolve this?
-
I trust you're using the latest service release for v10.1?
http://www.seagullscientific.com/support/service-releases-legacy-versions/v101/
How are the labels being printed? In BT directly, through Print Station, or something else?
You might want to contact tech-support directly for assistance.
0 -
Thanks for the reply Ian. Yes I'm running Bartender 10.1 SR4 and labels are being printed through the Print Station.
0 -
I've finally gotten around to talking to my local Bartender tech-support. They managed to replicate my observations and basically confirmed that this is a feature that would not be supported in Bartender 10.1.
I've got to say that this is rather disappointing as I had thought that serialization within the local label template would be a very basic feature that would be provided by a professional label management software.
Just to sum up the issue that I encountered:
* I deploy the Enterprise Automation version of Bartender 10.1 to a mass production environment in a factory
* Label templates are checked into the Bartender Librarian and users print labels through the Bartender Print Station
* Labels are set to serialize with every piece of label printed
* While serialization works fine within a print job, it appears that at the end of the print job, Bartender is having trouble checking the label back into the Librarian. As such, when a fresh print job is launched, the last used serial number is forgotten and the serial number starts from 1 again.
* This causes problems for my deployment as it results in duplicate serial numbers, which is a big no-no production of products which eventually gets shipped to consumers
My local tech-support team did offer a workaround which is to trigger serialization through a Global Database field. This works fine other than the fact that I run literally hundreds of labels that need to be serialized independently. As such, I would need to create hundreds of Global Database fields to support my application, which is a bother to manage, but I guess my choices are limited at the moment.
0
Please sign in to leave a comment.
Comments
3 comments