We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

MailMerge date field cannot handle ISO format after Aspose.Words version upgrade

Hello,

We upgraded from Aspose Version 15.2 to 16.10. Now the problem is that DATE mail merge fields no longer work.

The MailMerge field looks like this:

{ MERGEFIELD date_value DATE @“d. MMMM yyyy” * MERGEFORMAT }

date_value
was so far passed as a Date string of the following ISO format:

yyyy-MM-dd’T’HH:mm:ss.SSS zzz

Specifically, a date like this is not recognized:

2013‐09‐01T00:00:00.000 MESZ

Now after the upgrade, the date string is no longer convert to the “d. MMMM yyyy” format.

Only when I pass the Date string date_value in the following format, it is correctly converted to “d. MMMM yyyy”:

d MMM yyyy hh:mm:ss zzz

Why is the ISO format no longer recognized and converted into the desired format?

Is there any solution without having to change the format of the Date string passed as data?

Hi Adrian,

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 simple Java 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 them and Click 'Reply' button that will bring you to the 'reply page' and there at the bottom you can include any attachments with that post by clicking the 'Add/Update' button.

Hello Tahir

I have attached the input and output files as well as an example Java application that reproduces the bug.

Hi Adrian,

Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-14607. You will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.

The Aspose.Words v15.2.0 generates the same output. Could you please share the output document here for our reference?