Mail Merge- Inline .pdf attachments?
We have very complex mail merge templates for our Business Continuity and Disaster Recovery plans; these reports have to include up to dozens of attachments from Archer; we ideally want to display the contents inline.
Our default instructions are to use .doc or .docx format, but a number of our .doc/.docx recovery procedure attachments cause exceptions in the mail merge process that we assume are encoding errors- it most commonly happens in attached documents that use common reserved scripting characters. To get around this we tried converting these problematic attachments to .pdf format. This allows us to successfully export a plan into its mail merge template, but the mergefield [file].data element in the template isn't parsing this attachment format.
Is there anything else we can do to avoid encoding issues?
PS- We know code excerpts can cause these issues, but there have been cases where .doc or .docx files that did not have any obvious reserved characters in them threw the same error on export.
The attachment is inserted inline on a separate page. All attachments must be a Word (.doc or .docx) document. All other file types are not supported and are ignored in the exported file.
Note: ".Data" represents the field data of an attachment, which is how the data is retrieved
Maria if the attaching Word documents to a mail merge are "crashing" the mail merge process, open a ticket with support so they can take a look a log a defect if it truly an issue with the mail merge process.
Too late for this, but FYI, we isolated it as being an encoding issue through testing. We took certain characters out of the .doc/docx files and they merged properly. We wouldn't have been able to enforce validation to prevent our users from inserting those characters in the recovery documents, so we were looking for another solution.