I have a document that has an INCLUDEPICTURE field in it with a MERGEFIELD in the path of the image to be inserted. The resulting merged document has a broken image in it. There is also an INCLUDETEXT field in the document with the same merge field in it’s path and it works as expected. Below is an example of the source document.
{ INCLUDEPICTURE “{ FILENAME \p }\…\images\entity{ MERGEFIELD “ENTITY_NUMBER” }.jpg” }
{ INCLUDETEXT “{ FILENAME \p }\…\images\mydoc-{ MERGEFIELD “ENTITY_NUMBER” }.docx” }
The resulting merged document looks like this:
{ INCLUDEPICTURE “\…\images\entity.jpg” * MERGEFORMAT \d }
{ INCLUDETEXT “c:\path-to-my-doc\my.dot\…\images\mydoc-004.docx” }
The include text field has correctly been merged whereas the include picture field not only doesn’t have the merged data it doesn’t have the full path to the source document. The merged value of the ENTITY_NUMBER is “004”.
Is there a problem with the merging the INCLUDEPICTURE field or am I setting it up incorrectly?
@buddyackerman
Thank you for your feedback. We appreciate your interest in our product.
We see that the INCLUDEPICTURE field containing a MERGEFIELD in its path is not resolved correctly during the mail‑merge process in the online MailMerge application. This is a current limitation of the web tool – nested fields inside an INCLUDEPICTURE path are not processed, which results in a broken image link.
We have escalated this case for further investigation and to consider improving support for dynamic INCLUDEPICTURE paths in future releases. No additional action is required from you at this time.
@buddyackerman
Thanks for your feedback.
We apologize for any inconvenience caused.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID: APPS-100
As soon as this issue is resolved, you will be notified via this forum thread.
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
If you have any other questions, please write to us.
We will be glad to be of service to you.
Can I get some information about the fix for this? We’re talking about using paid support as this issue is causing a problem with a hard deadline to implement our solution. Feel free to contact me directly via email or give me a way to contact you about getting the priority for this issue raised.
Thanks.
I’ve also been thinking of an alternative that would require us to get access to the INCLUDEPICTURE field and modify it before it’s merged. Does Aspose have the ability to modify inserted fields like INCLUDEPICTURE?