Quick Question on Printing via system agent

Working on creating a function to print a pack slip report to a specific printer via the epicor system agent.

I tried bartender, but the bartender version I am on doesn’t quite have tabular data figured out and using the table function itself is very wonky.

In short, I feel like my way out is an SSRS report via system agent.

In any case, I want to print to a specific printer, because we do our packing at 1 location right now. I get that in the future it could grow and I could futureproof this, but I’m thinking shortsighted right now.

My question is, I’ll make the submit to agent call with the packslip print service and all that, but when I specify the printer, where do I need to install that printer so that it actually prints? I know the system agent is picking up the task, but what spooler is spooling it? The server where the task agent is installed? The client workstation that’s specified in the submit to agent call?

Anyone want to dive into explaining printing to me? I’m about to dig up Nathan A’s post on printing again. It’s been a minute since I’ve touched these BOs.

Thanks in advance for any enlightenment.

Do you have server side printing set up?

I have just client side set up in company config, if that’s what you’re asking:

image

But I don’t know if that limits me from doing server printing.

On-prem or cloud? Can’t remember on you.

On prem.

1 Like

Great, well basically everything you need is in Nathan’s post.

You’re gonna want to set up server side printing, otherwise you’ll need a logged in client.

Cloud would be more involved. Would want a server edge agent. Which I also assume would work in your case, but I don’t know the steps.

I found it for you too :slight_smile:

3 Likes

I think any server is fine (one might be quicker than another…).

Just know that you cannot reference an IP address in Epicor - you have to share it from the server and reference that path.

2 Likes

depending on your printer, it may have a server embedded that you can reference with a UNC path as well, including the IP ala \\10.1.1.37\whatever or \\myprinter\bla\bla

just not 10.1.1.37 without the unc path

3 Likes

Thank you both.

1 Like

I know that post well.

Here’s my thing. I don’t want each and every screen to now prompt the users to choose network printing or client printing, and I can’t see going away from client printing altogether.

Can I just do the rest of it aside from the company config and submit to agent that way?

I did a trace between using a network printer and a non-network and the only difference is this:


 <AutoAction>SSRSPrint</AutoAction>

vs

          <AutoAction>SSRSClientPrint</AutoAction>

Yup…shared/named printers on the app server and connected via IP. Make sure to install the correct printer driver as we had some squirrely performance early on…then reference the printer name from the app server in Kinetic.

2 Likes

Thanks for chiming in!

Wind chimes new GIF on GIFER - by Tho

4 Likes