Tuesday 28 May 2019

Edit emails with printed reports before sending them out from Dynamics 365 for Finance and Operations

Sometimes there is a need to check how an automatically generated email, e.g. with printed quotations or purchase orders looks like before we send it out from our Dynamics 365 for Finance and Operations. In my previous article you can learn how to preview such emails before sending using the Docentric free-edition tool. However, sometimes there is also a need to change something in the email body, for example, adding some additional attachments or email recipients to the generated emails. Luckily, you can do this very easily with the help of the same tool.

Let’s demonstrate this on the example of emailing the Customer account statement report (Accounts receivable -> Inquiries and reports -> Customers -> Customer account statement).

For this example, in the report dialog, I have selected one customer for which I want to print the report and I have changed the target print destination to Docentric Email.












In order to edit email with the attached report, we need to enable the "Open email before sending" option in the Print destination settings form. With this option turned on, instead of sending, the email will be downloaded so you can change the body, subject, and recipients or add additional attachments directly in your MS Outlook, before sending it manually.

Note: Above option is only applicable when not running in batch.























Now run the report, it will create and download the email as you can see in the image below.















Now we are going to add some additional information in the email which are as follows:

  1. Add a BCC email.
  2. Add an additional attachment, e.g. TermsAndConditions.pdf.
  3. Add a disclaimer to the email body.













That is all you need to do. Now you can simply send the email manually with changes.

No comments:

Post a Comment

How to fix Error: "Common Language Runtime detected an invalid program" in D365FO

Recently, we upgraded our environment, which resulted in one of our customizations, previously working flawlessly, throwing the "Common...