Bartender RDD from BAQ

Epicor ERP 10
1

I’m trying to use an RDD connected to a BAQ for a Bartender label. When I try to print or print preview, I get an error in the System Console:

Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: Value cannot be null.
Parameter name: key

Has anyone printed a Bartender label using an RDD from a BAQ? Any idea what is missing to cause this error?

2

I just ran a test in 2024.1.8 and Bartender from an RDD now works.
I see the text file being created in our Azure share and wjhen i open the text file it has labels and fields and looks normal.

Note: I also tried a BAQ Report to create Bartender Labels and I was not able to get that to work.

DaveO

1 Like
3

Dave,

I am using the BAQ RDD method to print Bartender labels. When I attempt to autoprint them I receive a 404 error from the task agent:


Failed to launch task to submit report. Error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> Ice.Api.Exceptions.UnknownRestException: HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

The output location and report btw file are in the same locations as our generic working labels.
I have a BAQ as an RDD data source with a criteria set. Anything I could be missing here?

4

@jgehling do you have print portal installed? I’d suggest going down that route using a function and pass in the baq… There are examples.

Here’s one

1 Like
5

What are you using for the Autoprint Parameters?

1 Like
6

image

1 Like
7

Mr. Jeff: Does your ReportID actually have a space in it? or is there an underscore there?

I have found that using spaces for BAQ’s or RDD’s (or Anything Epicor) can cause problems.

DaveO

8

Ah the problem was because I had the Run Schedule as immediate instead of queued (we are cloud)

9

OMG It works…

2 Likes
10

Yes! The criteria prompt stuff in the RDD is a little confusing for auto print params…but hey it works the Epicor way!

1 Like
11

Here’s something for posterity in case someone wants to see how it is done… I have not touched criteria prompts etc for ages, and it works.
DynBAQRpt_2024.2.7z (65.3 KB)

Looks like I am missing some bits like the source file path and the printer…

1 Like
12

Yes we noticed this as well and put in a case which has gone to development PRB0291011/ERPS-272502.

But thanks for your workaround changing it to queued which also works for us :slight_smile:

2 Likes
13

I’m still really struggling with this. I have everything working except for the selection criteria. I do get my bt file but it has tons of records in it, not just the current one. It does have my desired record first.

Am I supposed to user Criteria Prompts or Criteria Filters? Neither seems to include the choice of an operator type. Is it just always equal? Both seem to show up in the BPM as mappable fields, but neither seem to actually restrict my data.

14

For future posterity or when I forget this…

(in 2024.2)
It seems you must have BAQ Parameters defined first. I also had to set the criteria within the BAQ itself which seems like it should be unnecessary.

Then in the RDD, you can click the button to create Criteria Prompts under the Criteria Mapping section.

Then add the Criteria Set to the Report Style.

Now you should be able to wire up the parameters in the Data Directive for your Auto Print.

2 Likes
15

Hey Chad, yep that is what got me too! Exactly the steps I took.