aspose.zip (95.1 KB)
Attached is example solution with test merge data and test template loaded. When you try to process the template with this merge date this will crash on execute with regions.
However doing either one of the following will stop template from crashing:
- setting UnconditionalMergeFieldsAndRegions = false
- removing TravelInsured region from the template
- removing Secondary recordsets from the merge data
- fixing broken mergefield ‘RD_MDValuablesUV_TotalSI_JwlWatch_Worldw’
We are aware that underlying issue is that the mentioned mergefield is incorrect (and we are fixing this in our template) however we thought it was strange that the template would process without crashing if we eg. change UnconditionalMergeFieldsAndRegions to false.
We would really appreciate if you could review this case and either change the behavior (prevent processing of the template from crashing) or let us know what is the reason for this behavior so we could double check our code and templates to prevent similar issues in the future.