How to handle mailmerge of image that doesn't exist? What are best practices for handling image merge fields?

[FecklessFool]

Regular mergefields will just not merge if their data is missing/null.

Image mergefields however will throw an error if mergedata is null or if image doesn’t exist on Storage.

Not too sure if this worked fine in Total or if the old webservice that used Total was the one handling it, but some old templates broke due to null data or missing files.

What I’ve done is setup a default image when there is no data or if the image does not exist. If it exists upload all images to Storage before mailmerge.

But what is the recommended practice when it comes to handling image mergefields?

Thanks!

[awais.hafeez]

Hi Alfran,

Thanks for your inquiry. We managed to reproduce following error when data is empty string or null value:

Empty path name is not legal.

and the following error when we give path to the image that does not actually exist

Could not find file ‘image path’.

We are checking this scenario further and will get back to you soon.

Best regards,

[awais.hafeez]

Hi Alfran,

It is to update you that we have logged this problem in our issue tracking system as WORDSCLOUD-44. Our product team will further look into the details of this problem and we will keep you updated on the status of this issue. We apologize for any inconvenience.

Best regards,

[aspose.notifier]

The issues you have found earlier (filed as WORDSCLOUD-44) have been fixed in this Aspose.Words for Cloud update.

---

This message was posted using Notification2Forum from Downloads module by aspose.notifier.