Another thing you can do is Epicor has something called “Electronic Compliance” which lets you basically do a BAQ Report but it will output the BAQ to a XML or CSV. If you ever need to create your own Custom Label Event, you could then Invoke the EI in a BPM and it takes care of the rest.
Of course you can always make a BPM that writes the .csv out to BarTender yourself.
Good Item to Have:
The Electronic Interface (EI) stuff was a “tool” we had on the shelf for running custom code. We needed that in the “Multiple BAQ” reports to be able to support everything from calculated columns to stuff that could radically change how the report worked.
Another place that people probably don’t know even exists is Electronic Compliance. This area is much more general purpose than the name implies. Basically, this will let you take the output of an RDD and create an XML, JSON or CSV file.
Both the Multiple BAQ and Electronic Compliance were built at the same time. When you look at it from above, you start seeing the how and why.
Master @JeffLeBert