Advanced Print Routing: Group selected invoices by Customer

Hopefully this is an easy one. I am working with the SSRS Breaking/Routing and I’ve been able to get a simple workflow for sending individual invoices to customers breaking on the InvoiceNum for by AR Invoice Form style.
Break table = InvcHead


Break Column = InvoiceNum

Then, I hard coded to just send to myself.

I have a “mass print” selected invoices customization that just cycles through a list of invoices that a user types.
Putting in a few invoices and then selecting this print style works in that sends the attached invoices perfectly, so if I selected 3 invoices, it sends my 3 separate emails with the appropriate attachment.

What I need help with is grouping invoices by customers and sending the “group” of invoices to each customer.
Does anyone have an example of how to do so?

I’ve found the documentation on this tool non-existent.

Thanks

Since you are breaking by invoiceNum, each invoice is treated separately. Try breaking it by custNum or custID.

1 Like

I am getting ready for user testing of our AR Invoice form process and I setup a group by to to group on CustNum. As you I hardcoded my email in the send email action so all invoices are sent to me only.

image

image

Kristine

1 Like

I am not sure to understand your point or question. Sorry.

Thanks, I did get it to work with the customer group by assuming that I use the out-of-the-box functionality to print by breaking on cust num.
My issue seems to be more with how I’m submitting the individual invoices to the task agent via my customization, so I’ll take a look at that.

Thanks!

Thanks, breaking on CustNum does work, it just wasn’t playing well with what I had built on another customization so I wasn’t seeing the behavior I was expecting

What version are you on? Just a heads up I found during testing that we will need to be at 10.2.200.8 or later to get our APR process for Statements to use the Attach to DocStar functionality against the customer table. May not be applicable to you but wanted to share just in case.

10.2.200.3. I did find a bug (that was already reported) where you need to run in 32 bit mode in order to see the correct UI to interact with APR. We don’t use DocStar, so I probably don’t need to worry about that!

You might. The changes was made to APR functionality based on what I read in the release notes.

@kfierce did you run into any trouble with the conditional block?

I have a condition after the break to check the Customer.EmailAddress for both null and empty. If it’s not null or empty, it should send the email to the left.

The problem is, I am testing with customers that have no email and this still evaluates all the invoices down the “success” path and never down the “fail” path

Since null and “” are two different conditions, the logic states not equal to null OR not equal to “” will always be true. Should be not equal to null AND not equal to “”.

Thanks Brian, I tried that and it performs the same way. I also tried removing the pre/post fix to no avail

How about swap the logic so FALSE if = null OR = “” and TRUE otherwise?

I also tried that, but then they both route to the “fail” side of the condition. It’s like it’s not actually evaluating per Customer but it is breaking on invoice. I also put in a message variable to show the contents of the customer.EmailAddress field and they are different (one is blank, one has a value) so the data is correct

Reading through the release notes, there is mention about child table email addresses not being retrieved during the APR email process. I bet this is the issue they are describing. I’ll do an upgrade in DEV and see if it fixes the logic.

My send email condition looks like this and I have no problem with it. (saw it setup this way on a webex):

The CustomerEmailAddress report field on any row contains the @ value

With that any blank emails will goes down the false patch and gets printed on a network printer to go snail mail.

Kristine

2 Likes

Interestingly, that worked. I had to not put quotes around my “@” sign. Anyways, that helps, thanks

Kristine is correct - use the index/search on “@” character for true condition. that’s what we use.

2 Likes