I have a question about the use of repeaters in aspose.word. For some reason any text I place before the TableStart is duplicated, and I was wondering if this is a bug or by design. A simple example:
Names: <<TableStart:TableName>><<Name>> / <<TableEnd:TableName>>
The result I am expecting is:
Names: Name1 / Name2 / Name3 /
But aspose returns:
Names: Name1 /
Names: Name2 /
Names: Name3 /
Shouldn’t only the things between TableStart and TableEnd be repeated and not the things you put in front of TableStart?
If you need I could send you an example of a Word document in which this occurs.
Thanks for your inquiry. If you insert TableStart and TableEnd merge fields into the same paragraph, whole paragraph will be repeated for each record in your data source. This is by design. We will consider adding an additional mail merge syntax, which will allow repeating only part of paragraph. Your request has been linked to the appropriate issue. You will be notified as soon as it is resolved.
While you are waiting for this feature, you can try implementing a simple workaround using MergeField event handler. The idea is that you prepare string, which should be insert into merge field in your code. Let’s suppose you have merge field Names in your template (without regions). You need to insert list of names into this field. Here is a simple code, which will allow you to achieve this:
// Create a dummy datasource.
DataTable data = new DataTable();
data.Columns.Add("Name");
// Add some dummy data.
for (int i = 0; i <10; i++)
data.Rows.Add(new object[]
{
string.Format("name_{0}", i)
});
// Open template.
Document doc = new Document(@"Test001\in.doc");
// Add MergeField event handler.
doc.MailMerge.MergeField += new Aspose.Words.Reporting.MergeFieldEventHandler(MailMerge_MergeField);
// Execute simpel mail merge.
// As a value of th efield we put DataTable.
doc.MailMerge.Execute(new string[]
{
"Names"
}, new object[]
{
data
});
// Save output document.
doc.Save(@"Test001\out.doc");
void MailMerge_MergeField(object sender, Aspose.Words.Reporting.MergeFieldEventArgs e)
{
if (e.FieldName == "Names")
{
// Get DataTable with data and prepare strign, which should be inserted into the mergefield.
DataTable data = (DataTable) e.FieldValue;
string dataText = string.Empty;
foreach(DataRow row in data.Rows)
dataText += string.Format("{0}, ", row["Name"].ToString());
e.Text = dataText;
}
}
what if I had more than one field which would be formated differetnly?
i.e. - /
where name would be one font/color and phone number would be another?
would it still be possible to use this approach?
Thanks!
Igor
Thanks for your inquiry. Unfortunately, this approach will not work for few fields. So, you need to wait when this feature will be added into Aspose.Words or use the approach suggested by Adam in other your thread: https://forum.aspose.com/t/69800
Best regards.
Thank you for inquiry. Yes, we have logged it as new feature request as WORDSNET-3197 in our issue tracking system. Our team will look into this requirement and you’ll be notified via this forum thread once it is supported in future.
Regarding WORDSNET-3197, it is to update you that we have closed this issue. We have introduced a new LINQ Reporting Engine which is a part of the Aspose.Words API that enables you to build reports using an extended set of reporting features. The engine enables you to reference business objects of your application in report templates directly, which agrees well with Domain-Driven Design widely used in modern software development. Moreover, the engine uses a subset of C# language in its template syntax. These features enable you as a developer to compose report templates in a familiar and intuitive way.
For example, using this new reporting engine you can repeat part of a Paragraph as follows:
DocumentBuilder builder = new DocumentBuilder();
builder.Write("The items are: <<foreach [item in items]>><<[item]>>, <</foreach>>and others.");
Document doc = builder.Document;
ReportingEngine engine = new ReportingEngine();
engine.BuildReport(doc, new string[]
{
"Item1",
"Item2",
"Item3"
}, "items");
doc.Save("out.docx");