Has anyone gone down this road yet? We have purchased some Honeywell EDAs and want to start using handhelds, but we are having a very hard time being able to print our tags and have them come out with the proper font settings. The SSRS tags print very small when we print to our server printers. If we try printing SSRS tags to our server printers in regular Epicor, we get the same problem. If we do a Print Preview, it prints fine, but if we print straight to the printer, it prints small.
We also have a custom menu option to print a specific tag, but can this even be added to a menu within Kinetic Warehouse so we can use it?
I find it hard to believe that we are the only customers having this problem. We’ve talked with three people at Epicor to try and fix our problem and they can’t.
Mr. Randy: Have you tried previewing the tag first and then print from the PDF?
I have seen this happen when printing direct from a client printer. The standard epicor tag is formatted for an 8 1/2 x 11 page. I typically modify the tag so it only fits a 4 x 6 (typical label) and then the count tags print fine.
I’ll be watching the responses on this. We just bought EKW and I was asked today how label printing will work. There’s certainly an option in the app for printing labels, so I assumed it would work OK out of the box… Guess not, eh?
The internal problem that we can’t figure out is the Bartender Vs. SSRS headache. Plus, we have custom labels for customers and a menu item for a catch-all label we use, but we can’t figure out how to get it on the menu or the BPM to fire off of the button in EKW.
I can’t imagine this should be this difficult. They wouldn’t have released it otherwise, but we are struggling.
We created our own bartender labels to print using BPMs. we have tighter control of what prints and where it prints using workstations. PCID labels auto print when reporting qty from job and transactions on the floor. We dont receive off the handhelds yet, but we could print PCID labels when processing through EKW (EMWW).
We had to customize our labels so the effort was worth it for us.
We were able to get the Print Tags button in EKW to print bartender labels. We deployed 50 tablets to the shopfloor so it was critical for us to figure out. It was not easy to set up and it’s not well documented. We’re a cloud customer so it was even more difficult but it really works well once all of the setup is done.
If you haven’t done this yet, the MtlTags report needs to bet set up with a Bartender print style:
The label printers need to be added via Printer Maintenance and set as SSRS printers (yes, even though they’re not printing an SSRS report), and they need to be added to whatever server you have the Bartender integration installed on:
The downside is that depending on what the transaction type is, you have to select the correct report style every time. We have a WIP tag for ending production on a job, a receiving tag, a part ID tag, and are working on more.
Ryan Mongeau
I work with Randy Holndoner the originator of this topic.
We have 80 Zebra printers on our network for Bartender labels.
The same 80 Zebra’s are also connected locally via USB for printing SSRS labels. If I try and print a SSRS label from EKW to our network printer, the print comes out real small.
Is it possible for me to discuss your setup over the phone with you?
Please advise. Thanks you.
We do the same as Bryan. We are rolling out EMWH for receiving and such soon. For BT i dont use the 1980’s style file drop, I configured it for webservice which is absolutely amazing as you can see immediate (real) feedback. As for the plan on injecting this into a non-modifiable EMWH screen, I just plan to high jack the incoming task and steal it before the task agent even gets it (and use that data to generate my BT call) - this way the user screen\experience should work seamlessly.
Not sure what issue you’re having, but I am indeed running Automation and not Enterprise.
In terms of accessing the API, this is the entirety of the custom code block I put in a BPM that fires off when a specific job op is completed.
For your integration, just just have to swap in your bartender server name and the name of your integration in the uri variable at the top. The rest is configuring the loop or lookup to your specific case.
string uri = "http://ServerName/Integration/IntegrationName/Execute";
foreach (var row in ttLbrScrapSerialNumbers)
{
HttpWebRequest hwr = (HttpWebRequest)WebRequest.Create(uri);
hwr.Method = "POST";
using (StreamWriter sw = new StreamWriter(hwr.GetRequestStream()))
using (JsonTextWriter jtw = new JsonTextWriter(sw))
jtw.WriteStartObject();
{
jtw.WritePropertyName("sn");
jtw.WriteValue(row.SerialNumber);
jtw.WritePropertyName("pn");
jtw.WriteValue(row.PartNum);
}
jtw.WriteEndObject();
hwr.GetResponseAsync();
}
Also, for your own sanity, make sure you’re using Seagull’s Zebra drivers.
EDIT: Reworded a few things for clarity.
EDIT2: After reviewing my other integrations, you don’t need to set the Formatting property. Also, BT doesn’t support sending more than one object per post, which is why everything is inside the loop.
So this does get me outside of the BT docs with Print Portal (and presumably the Swagger page as well), but I will take what you have sent and start testing.
I know it’s a little ways off, but I will be presenting a discussion on BT web service at Insights this year.
A few generic tips to start:
Dont try to get fancy with auth until you are done developing\testing
You can use POST or GET - use POST, it’s more flexible (send params in body)
@TyrusRechs This is excellent - what a crazy find. This saves (me) a ton of time.
So I see now that this is part of regular old receipt entry in EKW, but you don’t have the option to choose a printer in the client, so it just fails there.
