MergeFields popluated with data from different region

[dgarcia_aspose]

I have a template which uses many regions. These regions are similar in nature where they have same column names, but we load different data into them.

Just recently, we noticed that our template that has worked fine for a long time, started to confuse the mergefields in one region with the field of another. For example,

TableStart:Region1 …TableEnd:Region1

TableStart:Region2 …TableEnd:Region2

Our situation is that Field1 in Region1 goes blank and the value of Field1 in Region2 gets the value that should have gone into Region1’s Field1. The column names are the same, but the data is a little different, so we can tell its the value for the datasource of Region1 and not from the datasource of Region2.

Any suggestion on how we can fix this issue. I know we could just rename the mergefields to each have their own unique names, but it worked before and rather not have to change a bunch of template because of this new “bug”.

Thanks in advanced.

[tahir.manzoor]

Hi Daniel,

Thanks for your inquiry. It would be great if you please share following detail for investigation purposes.

• Please attach your input Word document.
• Please

  create a standalone/runnable simple application (for example a Console
  Application Project) that demonstrates the code (Aspose.Words code) you used to generate
  your output document

• Please attach the output Word file that shows the undesired behavior.
• Please share if you are facing this issue after upgrading the Aspose.Words version.

Unfortunately,
it is difficult to say what the problem is without the documents and
simplified application. We need your documents and simple project to
reproduce the problem. As soon as you get these pieces of information to
us we’ll start our investigation into your issue.