Nested Mail Merge with Regions

In some scenarios, you may need to use nested mail merge with regions. Nested merge is a feature that allows you to merge hierarchical data from your data source into your merge template to easily populate your document. Basically, the hierarchical data is represented as a set of data items, and hierarchical relationships describe how the data items are related to each other (one item of data is the parent of another one).

Aspose.Words enables you to perform a mail merge operation with nested regions. You can use this feature if you have a data source that is organized into a tree-like structure and you want to execute a mail merge operation to populate a template with hierarchical data.

What is a Nested Mail Merge

The mail merge region is called nested if you have two or more mail merge regions where one of them is inside the other in a hierarchical form. Note that each region contains data from one table.

The most common example of a nested mail merge is an order that contains a few items where you need to link many data tables and present the information in a template.

The picture below demonstrates two nested regions where the Order mail merge region is the parent of the Item mail merge region.

nested_mail_merge_with_regions

How to Process Mail Merge with Nested Regions

The data to be merged into a template can come from various sources, mainly relational databases or XML documents. In our example, we are going to use an XML file to store our data and load it directly into the DataSet.

Aspose.Words allows you to process mail merge with nested regions using the data relationships specified in the DataSet. When the DataSet object loads XML, it either uses the provided schema or infers it from the structure of the XML itself to accomplish this. From this structure, it creates relationships between tables where necessary.

The image below demonstrates how the data from the Order table passed to the nested merge regions will be linked to the Item table, as well as the output generated during the merge operation.

mail_merge_with_nested_regions

As you can see from the output document, each order from the Order table is inserted into the merge template with all order’s related items from the Item table. The next order will be inserted along with their items until all the orders and items are listed. The order of nesting mail merge with regions in the template must match the data relationships between the tables in the data source.

The following code example demonstrates how to generate an invoice using nested mail merge with regions:

How to Set Up Data Relations in Nested Mail Merge with Regions

You need to set up all data relationships in the parent-child structure to execute the nested mail merge with regions correctly. Skipping this important step can lead to a failure in executing the nested mail merge with regions.

When retrieving data for a nested mail merge from an XML file using the ReadXml method, relationships are automatically created according to the structure of the XML document. However, you need to make sure that correct relations have been created.

If mail merge is not working as expected, then you may need to restructure your XML file or explicitly create relations between DataTable objects in the DataSet.

A DataSet that has related data tables will use the DataRelation object to represent the parent-child relationship between the tables.

The following code example shows how to establish a DataRelation between a customer’s table and an order’s table by using a DataRelation object:

How to Create Data Relations from a Custom Data Source

Implement the IMailMergeDataSource interface to create relationships in the parent-child structure of your custom data source. Use the GetChildDataSource method to return the relevant child data of a current parent record.

The following example shows how to create data relations using GetChildDataSource:

.NET

public IMailMergeDataSourceCore GetChildDataSource(string childTableName, bool isObjectAttr)
        {
            DataRow parentRow = GetCurrentDataRow();
            DataTable parentTable = parentRow.Table;

        	DataSet dataSet = parentTable.DataSet;
       	 if (dataSet == null)
            	return null;

            DataRelation childRelation = FindRelation(dataSet, parentTable.TableName, childTableName);
            if (childRelation != null)
            {
                // Normally expected, found a relation to the child table, return a data source for it.
                return new MailMergeDataSourceDataRelation(mMailMerge, parentRow, childRelation);
            }

        	if (!isObjectAttr)
        	{
            	DataTable newTable = dataSet.Tables[childTableName];
            	if (newTable != null)
            	{
                	// No relation, but such a table exists in the dataset. It means an unrelated table.
                	// Return all rows of the table as per the interface specification.
                	return new MailMergeDataSourceDataTable(mMailMerge, newTable);
           	 }
        	}

        	// No relation and no table, means mismatch between the template document and the data set structure.
        	// Return null as per the interface specification.
       	return null;
   	 }