Sending Email Notification through Routing Method

Epicor ERP 10
,
1

The email notification to be sent based on the salesrepcode-

In the existing the mail notification is sent through the Routing method, by default the email is sent to the customer , along with the customer we need to sent the mail to particulat ISS or RSS salespersons. If the orderhed is in ISS we need to send mail to ISS Salesperson or If the orderhed is in RSS we need to send mail to RSS Salesperson

Now the issue - there is no relationship present for salesrepcode column in RDD…in orderhed the salesrepcode columnn is kept using delimiter …Also there is no way to use calculated field in RDD

So, what’s the way to create a relationship in RDD?

2

First you need to duplicate the report data definition. And then you need to add the table to the new report data definition. You may also need to create a new report style, but I am not sure. I recall a post on here saying that your RDD won’t update in the routing screen unless you do X Y Z, but I think creating a whole new report style will let you see the newly added fields.

  1. Look up how to add a table and a relationship to a report data definition
  2. Do that
  3. Create a new report style*
  4. Create the routing with the newly added fields.
3

@utaylor Hello Utah thanks for the Reply , However my Question is can we create a Calculated column in RDD to breakdown the Delimited Data , and Using that Column i have to Create a Relationship between Table:SalesRep.

Example :101~102~103 this is sales rep list code in OrderHed Table , i have to Seperate the Each SalesRepcode to find it’s Corresponding Value in SaleRep Table .

I can do this in SQL or BAQ , But i want to do this in RDD Relationship to Find the Sales Rep Email for Corresponding List . How to break the Sales Rep List and join it in RDD

4

In order to get our Sales Rep on our Order Acknowledgement email, I had to go from the OrderHed to the ShipTo and then from ShipTo to the SalesRep. But I am only trying to get the primary sales rep, so I don’t think you could do that.

What I would do in your case is the following.

  • Add the SalesRep table to the RDD with no joins. If your table is rather large, filter it by something to make it smaller.
  • In the report Dataset query, add the Sales Rep table 5 times and link each sales rep code to the sales rep table.
1 Like
5

Great idea john, but to use each of the 5 emails in the routing email action you would need those in your RDD dataset, not the report dataset in the .rdl.

And I don’t think you can add the same table more than once unless they have fixed that.

1 Like
6

I don’t think you can make a calculated field in RDD. I could be way wrong though.

7

You are right. I was not thinking about the routing, just the report.

1 Like
8

You can if you have the SDK.

9

I am assuming @Atchaya does not have that, but yes you can if you have the SDK!

10

Just to add a few details to this: for #2, the relationship for conditional and field availability must be linked directly to the “Break Table” or downstream (at least in Kinetic 2021.2 where I’m testing) within the RDD. For instance, if you break a packslip on ShipHead, tables like Customer will not be available unless you re-link their relationships through the ShipHead table instead of through OrderHed.
For #3, you do not need to create a new report style. The only caveat is that if you’ve already created a routing and then you change the name of the RDD or add a new table relationship that a report is using, you’ll need to delete the routing and recreate it because the RDD ID and available tables are instantiated at the time of creation.

To the original poster, because of the caveat mentioned above about routing, I might consider instantiating the target email to a UD field on OrderHed using a BPM on change of customer or shipto so that it is natively available for addition in the RDD as well as the routing when breaking on OrderHed.

1 Like