Ok, I am doing my code review, and I am here:
FWIW, using a Function was a great idea. If you want to change your method later, everything is encapsulated and you only have to change the function and not every place you call the API. So, +1 Obi Wan.
Now I have to go back and move some of my BT label generation code to functions as well.
Functions were not mature enough when I started.
My label generation stuff is all run off of two BAQs
One is a BAQ with subqueries as unions that generate different types of labels mapped to a
somewhat generic dataset.
The other is a UBAQ with the BPM logic to do the logic, allow overrides, passhthrough data printing
etc.
It’ll be a treat to rework lol 
I’m curious, are you on-prem? I tried working with our consultant for a REST solution on cloud hosted, but it seemed like there weren’t any methods to get Epicor SaaS to establish a direct connection to our self-hosted bartender server.
All I have to say is that the 2019 web integration responses are less than helpful when there is an error and handling errors and presenting meaningful pop-ups to your users is difficult but you should spend some time figuring that out for yourself and for them.
I am also inexperienced when it comes to APIs and coding integrations, but this proved extremely difficult to me. Have you found any API documentation of theirs for responses and error messages?
1 Like
No, SaaS - Public Cloud.
I upgraded to Bartender 2022 R4.
To tell the truth I didn’t look real hard. I figured I’d dig into it later if I wanted to provide detailed
information or advanced functionality. I just wanted the basics, print, request ok/fail.
We did the same, and no one had any answers at the time.
I only had experience with Vantage. We abandoned Bartender with
Vantage in 2009, so I had no experience with Bartender either really.
I got some bits and pieces from here, which is basically where I learn everything, and today
it really shouldn’t be a problem with a competent programmer and/or consultant.
1 Like
Once in the cloud, there are other patterns people use than we do on-prem. One pattern you may consider is writing the request to an Azure Storage Queue. You then have an on-prem service that waits on the queue and processes the request when they arrive. This would be an Azure version of Kevin’s UD Table solution above. It’s also more secure than direct access.
2 Likes
Nice. I think you mentioned that before.
Ok
I am glad…
The hard part is the 201. Where it’s successfully there but doesn’t finish or something like that. Like the integration runs but user is just sitting there wondering what happened.
That’s my favorite part!
Unless I am the user. Then I don’t like it.
My users don’t like it, I don’t like it either cause their problems are my problems.
1 Like
Yes, at some point I will be providing feedback.
Oh! Great work! Very interested in seeing your implementation, we have been struggling in this area.
2 Likes
I have also struggled to some degree. Kevin, can I ask if you use the same type of printer everywhere in your shop to print these labels?
Are they color by chance?