Free Support Forum - aspose.com

Unexpected end of children nodes reached (Aspose.Words.Reporting.MailMergeCleanupOptions.RemoveEmptyParagraphs)

Aspose.Words Product Family
#1

Hello. I just posted an issue i came across when using

document.MailMerge.CleanupOptions = Aspose.Words.Reporting.MailMergeCleanupOptions.RemoveEmptyParagraphs

The behaviour pretty much fits to the thread found here:
http://www.aspose.com/community/forums/permalink/363086/363086/showthread.aspx

However in this case the Version is 11.9.0.0 .net 2.0.

Generating the Document without MailMergeCleanupOptions.RemoveEmptyParagraphs works perfectly fine. the structure of the template used to display the data is the following:
<

>
<>
<<b.somefield>>
<<b.someotherfield>>
a b c d e
f g h

<</inner table b>><</table a>>

i need to get rid of the spaces caused by the closing tags.

A swift reply to resolve this issue would be highly appreciated.

#2

Hi,


Thank you for your request. With high probability your issue has been fixed recently (WORDSNET-7129) and the fix will be available in the new release (11.10) coming very soon. However, in order to make sure, could you please provide your sample template and code snippet used for merge?

Thank you again and sorry for inconvenience.
#3

Hello again.

I have added the sample files now. It’s not the actual files because it is part of a project we are working on but it resembles the original structure to some extent.

What is the estimated release date on 11.10 if i may ask?

No problem by the way. We do however plan to finish our project by the end of this year. Hopefully 11.10 fixes this issue.


#4

Hi Patrick,


Thanks for your inquiry. While using the latest version of Aspose.Words i.e. 11.9.0, I managed to reproduce this exception on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-7373. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best Regards,
#5

Hello Awais,

Thanks a lot for confirming the issue. Let’s hope this issue might already have been addressed in the upcomming version as your collegue pointed out.

Thanks for your time and good luck with the bug fix in case it hasn’t been adressed yet.

Best regards.

#6
Hi Patrick,

We also hope for that as well. Regarding your original issue, we will be sure to inform you of any developments.

Best regards,
#7

Hi Patrick,


It is to inform you that your issue has been implemented in the current code base and the fix of WORDSNET-7373 will be included in the next release of Aspose.Words (11.10.0) that is due out at the end of this month. We will inform you as soon as the new release is published.

Best regards,
#8

Hi Awais,

Thanks a lot for letting me know. Can’t wait to update the component and check it out.
Thanks again for the time and effort.

Best regards

#9

The issues you have found earlier (filed as WORDSNET-7373) have been fixed in this .NET update and this Java update.

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

Hello again.

I have just update the component to check out wether it’s working now or not.

What i found out is that using this option now does not result in errors anymore. However using the “feature” seems to have no effect whatsoever.

template is like

DOCUMENT
HEADLINE
{{#foreach iteration}}
table
{{/foreach iteration}}
DOCUMENT

expected result:
DOCUMENT
HEADLINE
table
DOCUMENT

Actual result:
DOCUMENT
HEADLINE
EMPTY PARAGRAPH
table
EMPTY PARAGRAPH
DOCUMENT

Looks like this feature is broken or something. At least in 11.10 it doesn’t seem to work the way i’d expect it to.

On top of that other sections now ceased to work.

Template:
{{#foreach Windload xsi:type}}
Output:
«TableStart:“Windload xsi:type”» (used to be the same without brackets)

-> table contents are not beeing mergereplaced

#11
Hi Patrick,

Thanks for your inquiry. Please remove those paragraphs that contained mail merge fields with no data from the document by using the following option:

MailMerge.CleanupOptions = MailMergeCleanupOptions.RemoveEmptyParagraphs;
Patrick:
On top of that other sections now ceased to work.

Template:
{{#foreach Windload xsi:type}}
Output:
«TableStart:"Windload xsi:type"» (used to be the same without brackets)
While using the latest version of Aspose.Words i.e. 11.10.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-7415. Your request has been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
#12

Hello Awais,

Unfortunately that’s the problem. I am using

MailMerge.CleanupOptions = MailMergeCleanupOptions.RemoveEmptyParagraphs;

which does not throw an exception anymore now but does not remove empty paragraphs either.

Thanks however for already adressing the other issue.

Best regards
#13

Hi Patrick,


I would like to apologize for inconvenience too. We are currently analyzing your issue and will update you with the latest progress ASAP. What we have found so far (yet this unlikely has to do with your current issues) is that the simple fields in your template are only enclosed in single brackets (like {field}) while expected to be enclosed in double brackets (like {{field}}). But this is just a remark.

Thanks.
#14

Hello Dmitry,

I just checked out the sample file i provided. Turns out my provided sample actually contains errors for the described fields. The behaviour i am describing though was on our Application where the fields are written with double brackets. But good catch there.

I will ask my boss if it’s ok to provide actual production data for you to validate the behaviour. But i can’t make any promises on that yet.

Best regards

#15

Patrick,


That would be great of course, since we can then make sure that the issue is completely fixed for you this time. You can replace all sensitive data with random text if needed. Currently we are working with your sample template you provided earlier. And the responsible developer has just completed the analysis; we have found the cause of the issue and will proceed to development shortly.

Thanks.
#16

Hi Patrick,


Regarding your problems you’re getting with MailMergeCleanupOptions.RemoveEmptyParagraph option, could you please double check if these are occurring when using your ‘template.docx’? I have also attached output document here for your reference. Could you please create a screenshot that highlights which Paragraphs you would like to remove from your final report? Thanks for your cooperation.

Best regards,
#17

Hello Dmitry,

I uploaded another sample with the sections which fail to render as expected after updating to 11.10.0.0

This is only a snippet of the actual production document but i am certain my boss won’t mind me sharing this part.

The reason we iterate through the template using
{{#foreach Windload xsi:type}} is that the full xml contains another property called Windload on the same tree level.

I spent some time trying to figure out what could be the reason as to why this would fail.
- not surrounding with “Silo” foreach first (still works in other areas right now). could it be an “accidental” feature which we abused? and in the latest version it might have been been fixed partially because it wasn’t intended?
- output generates MERGEFIELD “TableStart:Windload xsi:type”. maybe the replace engine expects a pattern like MERGEFIELD TableStart:“Windload xsi:type” ?

Anyways. I hope the provided sample is usefull in finding the problem in some way. I guess to fix the empty paragraph issue the other template will suffice.

Best regards


#18

Hello Awais,

I have now checked out the template and the output again and took the screenshots you asked for.

I noticed one behaviour in particular (which i haven’t noticed before because i always checked in a certain area of the output document). For the majority of the document the cleanup option actually seems to work but apparently stops working properly once the given table exceeds a page.

in template.png you will see the table starts top right (page 2) and ends on bottom left (page 3)

The paragraphs are marked (with horribly bad drawn) arrows.

On output.png you can see that removing the first paragraph actually did work, while the paragraph at the end of the table did not get removed

I hope that helps zipping up this issue. I really have to thank both of you for this remarkable support.

Best regards

#19

Hi Patrick,


Thanks for the additional information. I have tested the scenario and have managed to reproduce the same problem on my side. For the sake of correction, I have logged this problem as WORDSNET-7421 in our issue tracking system. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

Best regards,
#20

Hello awais,

I was wondering how long you’d reckon fixing this issue would take and at which point an updated .dll is available. As i’ve mentioned we’re aiming at finishing our project by the end of this year. If you don’t think it’s possible by then it would just be nice to know so i can prepare for that. No pressure intended.

Have a nice weekend.

Best regards