By using this website, you agree to our Terms of Use (click here)
I have a situation where I want to send an email to an employee (salesperson) when an account they are assigned to changes their status. I have a GI that pulls all the info I need together. I then use that GI in a business event that is triggered by a record change. I have a subscriber in that business event that send the email out to the salesperson. I have everything working when I use my email address as the "To" in the email. Now that I am done testing and I want to start sending out to the email address in the GI, it stopped working. The email gets generated, but the "To" field is always blank, so it doesn't send out. I use the selector to navigate to my GI email field and I get the following:
If I use the same code in the body of my email, the email address does not show up. I use all the other fields in the GI in the body of my email and I have no issue, it's just this email field. I also completely rebuilt the GI, the business event and the notification template and I still cannot get it to work. What is even more frustrating is that I have a similar setup and the email field shows up just fine. I have tried everything I can think of but I cannot get that email address to pull into my email. Any help would be much appreciated.
My GI relationships go from: Customer -> CustSalesPeople -> SalesPerson -> EPEmployee -> Contact
The relationships and the linking all appear to be working because I verified the data and all the email addresses are correctly showing.
I find business events/notification templates can be very finnicky. I was in a similar situation recently doing some business event/notifications on requests/purchase orders. I had to keep playing around with the GI until the notification template took my email field (even though it was there all along just like in your situation). If you have covered all routes with the CR.Contact table you could try to create a text attribute for customers -- then fill their email out on the attribute field. You would use the CS.Answers table instead.
I have found them to be very finicky too. I'm looking forward to a session on Business Events at Acumatica Summit 2023 where I'm hoping to learn more about troubleshooting them.
We recently upgraded to 2022 R1 and this problem went away. The code I used above in the "To" field started working without me changing anything.