Here is the signature for my generic func to REST call BT.
I have the most common data broken out as individual params. For the key data, I just pass in ~ separated keys that get parsed. There are certainly fancier options here - like pass in a json object.
LabelType determines the BAQ to use, LabelFormat is the BTW template to use.
I have some logic that determines what BAQ to call, and which params to use.
Then it calls the BAQ, parses the data, sends to BT
Exactly! Yeah man I need to just have it stop waiting the response cause it’s terrible to wait.
Thank you.
This is nice.
I have wanted to do this just haven’t had the time to focus on re-doing this mess.
Yeah when I wrote mine, I turned that off.
Just gets hard for operators cause when there is an error at least they can see it if I wait for the response.
I’m not currently using mine, but what I actually did was call my own api.
Since I’m calling from the cloud and not using print station, I wrote my own minimal api. (So I could secure it.)
My api is fire and forget.
You could do the same, but log responses back to epicor (from the minimal api, via epicor function), and they could see a dashboard.
Then, they don’t have to wait, but they could see something was up if there was a problem.
Thanks for the idea, never wrote my own API before so that’d be a journey… just out here trying to survive and soak up as much as I can from your posts and other experts on here so that one day maybe I can use it.
Frankly if you don’t need all the bartender functionality and can do it with SSRS, then why not. There goes some savings with regards to per printer licensing that you don’t need to spend on
Minimal API made it stupid simple.
I’ll revisit mine after Insights and share a slimmed down version.
Awe…
My copy will be released after Insights. Still got some documentation to do to make it a useful package.
In short:
A series of UD codes that allows you to configure for any label and BAQ pair
More UD codes to configure your environment (Bartender REST or Integration Web Service).including SSL enabled or not.
Function that accepts the relevant BAQ parameters in a delimited key pair values, so if your BAQ any number of parameters you can use them.
It does not log anything to UD tables like @Chris_Conn 's solution does. Baring in mind that Bartender already does that stuff with History Explorer and the Reprint Console.
I ended up concentrating more on the REST API rather than the web service integration and I do have copies functions that work for the web services, but my limited abilities couldn’t get my head around the JSON variables in the integration (CSV did work), scouring the Bartender KB, made me think that the JSON stuff was not implemented well in the Web Service Integrations.
I also think that this will work with Cloud and with a bit of effort with Bartender Cloud (it uses Tokens, which is not implemented in on-Prem)
So if you want to get an understanding of the Different methods of using Bartender, then come along (Hecklers accepted)…Just keep it to a dull roar if you please. 
You can do that with SSRS. I believe MtlTag already has this type of design.
Bartender also allows you to do this, but it is very challenging. I think the newer version of Bartender handles this best.
Talking about REST Ssrs has its own REST api sir maybe there is some scope there
I am looking forward to this, but I may be speaking in a separate session at the same time 
When is your session?
