Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:
Your input Word document.
Please attach the output Word file that shows the undesired behavior.
Please create a standalone console application (source code without compilation errors) that helps us to reproduce your problem on our end and attach it here for testing.
As soon as you get these pieces of information ready, we’ll start investigation into your issue and provide you more information. Thanks for your cooperation.
PS: To attach these resources, please zip and upload them.
Thanks for your inquiry. Please use latest version of Aspose.Words for .NET 18.4 and LoadOptions as shown in following method to get the desired output. We have attached the output PDF with this post for your kind reference. 18.4-output.pdf (19.5 KB)
Please note that we do not provide support for older released versions of Aspose.Words. Moreover, we do not provide any fixes or patches for old versions of Aspose products either. All fixes and new features are always added into new versions of our products.
We always encourage our customers to use the latest version of Aspose.Words as it contains newly introduced features, enhancements and fixes to the issues that were reported earlier.
Ok, i understand.
In this case, is it possible to replace in the fly the field { IMPORT " {MERGEFIELD logo }" \d } by a mergeregion (like {MERGEFIELD TableStart:Logo} { MERGEFIELD Image:ImageLogo} {TableEnd:Logo})?