Printing and Routing using callContextClientData?

New to using Breaking and Routing, but I do not see a way to tie the callContextClientData to UserFile (for email address) in Routing and Breaking. I can do with the ChangedBy/CreatedBy fields but not the user actually doing the reporting so they get a copy of the report/pdf.

:thinking: :face_with_diagonal_mouth: :exploding_head:
Anyone with ideas?

Most RDDs have at least one table that has a calculated field UserID, you can then relate UserFile to get the current users email

5 Likes

Nice! Thank you found Calc_RptUserID on Customer table to link to UserFileList :slight_smile:

2 Likes

Another approach IF your Epicor user ID’s match your email addresses… you can ā€œInsert System Constantā€ and pull in the ā€œCurrentUserIDā€. Then just append to the value to complete the email address with your @whatever.whatever

image

1 Like

Very true, but just in case they ever don’t linking back to the EMailAddress in the UserFile, I avoid someone not doing what they should and breaking it :slight_smile:

2 Likes

Are we editing the RDD to get UserFile in this case? My understanding is that breaks existing routings. If so, we have to redo routing from scratch, true?

I am not aware of making modifications to RDD’s with existing routings breaking anything… unless of course you remove a table or columns the routing is using, or the routing is using a base RDD. Might run into a problem there, been awhile since I used APR

Thanks. Was told that at ARP EE, Insights '25. Perhaps I misunderstood. Perhaps not breaking but that RDD changes are simply not picked up by existing routings neccessitating re-do from scratch. Something like the routing ā€˜saves’ the RDD schema at creation and doesn’t update or some such. :man_shrugging: