You are currently offline, serving cached version

This module exposes a tag to include a subtemplate (another Word document). The subtemplate is embeded into your document. Only the document content is embedded, footers and headers are not since they are unique for each document, so the module keeps the headers/footers from your base template.

The styles of the resulting generated document will be the same as the styles from the main template, which means that styles that exist in both the template and the included document will use the styles of the main template. Hence, if both your main template and your included document have Heading1, the style that will be applied to all Heading1 will be the style from the main template.

Usage

Your docx should contain the text: {:include subtemplate}.

In your data, the key subtemplate should be another docxtemplater instance.

Usage (nodejs)

const SubtemplateModule = require("docxtemplater-subtemplate-module");

const headerZip = new PizZip(fs.readFileSync("header.docx"));
const footerZip = new PizZip(fs.readFileSync("footer.docx"));
const headerDoc = new Docxtemplater().loadZip(headerZip);
const footerDoc = new Docxtemplater().loadZip(footerZip);

const zip = new PizZip(fs.readFileSync("template.docx"));
const doc = new Docxtemplater(zip, {
    modules: [new SubtemplateModule({})],
});
doc.render({
    subtemplate: headerDoc,
    footer: footerDoc,
});

Usage (browser)

<html>
    <script src="node_modules/docxtemplater/build/docxtemplater.js"></script>
    <script src="node_modules/pizzip/dist/pizzip.js"></script>
    <script src="node_modules/pizzip/vendor/FileSaver.js"></script>
    <script src="node_modules/pizzip/dist/pizzip-utils.js"></script>
    <script src="build/subtemplate-module.js"></script>
    <script>
        function loadDocument(file) {
            return new Promise(function (resolve, reject) {
                PizZipUtils.getBinaryContent(
                    file,
                    function (error, content) {
                        if (error) {
                            return reject(errror);
                        }
                        resolve(content);
                    }
                );
            });
        }

        Promise.all([
            loadDocument("demo_template.docx"),
            loadDocument("examples/demo_header.docx"),
            loadDocument("examples/demo_footer.docx"),
        ])
            .then(function (documents) {
                var doc = new docxtemplater(
                    new PizZip(documents[0]),
                    {
                        modules: [
                            new DocxtemplaterSubtemplateModule(),
                        ],
                    }
                );
                var headerDoc = new docxtemplater(
                    new PizZip(documents[1])
                );
                var footerDoc = new docxtemplater(
                    new PizZip(documents[2])
                );
                doc.render({
                    header: headerDoc,
                    footer: footerDoc,
                });
                var out = doc.getZip().generate({
                    type: "blob",
                    mimeType:
                        "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
                });
                saveAs(out, "generated.docx");
            })
            .catch(function (err) {
                console.log("error while loading documents");
                console.log(err);
            });
    </script>
</html>

After installing the module, you can use a working demo by running node sample.js.

Subtemplate Rendering

You can render the values in your subtemplate by using a custom parser and render the document with the current scope.

For example :

const SubtemplateModule = require("docxtemplater-subtemplate-module");

const expressions = require("angular-expressions");

const headerDoc = new Docxtemplater(new PizZip(documents[1]));
const footerDoc = new Docxtemplater(new PizZip(documents[2]));

function recursiveParser(tagString) {
    return {
        get(scope, data) {
            const isIncludeTag =
                data &&
                data.meta &&
                data.meta.part &&
                data.meta.part.module ===
                    "pro-xml-templating/include";
            let value = null;
            if (tagString === ".") {
                value = scope;
            } else {
                value = expressions.compile(tagString)(scope);
            }
            if (isIncludeTag && value) {
                value.render(scope);
            }
            return value;
        },
    };
}

const doc = new Docxtemplater(zip, {
    modules: [new SubtemplateModule({})],
    parser: recursiveParser,
});

doc.render({
    header: headerDoc,
    footer: footerDoc,
});

Including multiple documents with a single tag

Note that it is possible to include several documents using the tag : {:include docs}, by simply using an array of documents in the related data attribute.

const includedDoc1 = new Docxtemplater().loadZip(includedZip1);
const includedDoc2 = new Docxtemplater().loadZip(includedZip2);
const doc = new Docxtemplater(zip, {
    modules: [new SubtemplateModule({})],
});
doc.render({
    docs: [includedDoc1, includedDoc1],
});

Subsections

It is possible to include subsections, however, if you only have access to the subtemplate module, the headers will not be included.

If you have access to the subsection module, you can do the following to also include the headers and footers of the included document :

const SubtemplateModule = require("docxtemplater-subtemplate-module");
const SubSectionModule = require("docxtemplater-subsection-module");
const doc = new Docxtemplater(zip, {
    modules: [new SubtemplateModule(), new SubSectionModule()],
});

When using the SubSectionModule with the SubtemplateModule, by default, the section where your tag {:include doc} is kept, meaning that it will create a pagebreak before adding the document, and also at the end of the included document, it will create a pagebreak.

If you would prefer to not have this pagebreak, than the currentsubsection of the document is going to be replaced by the one from the subtemplate. To do this, you have two attributes that you can set on the included document, replaceFirstSection and replaceLastSection :

var includedDoc = new Docxtemplater();
includedDoc.loadZip(new PizZip(includedContent));
includedDoc.replaceFirstSection = true;
includedDoc.replaceLastSection = true;

doc.render({ included: includedDoc });

Segments

The SegmentModule is part of the same package, and allows you to define a "segment" in the document that can then be included multiple times in the document.

You can use it like this in your template :

{:segment test1}
This is the segment 1
It can contain all {tags}.
{:segment/}

{#users}
{:includesegment test1}
{/}

In your code, write like this :

const SegmentModule =
    require("docxtemplater-subtemplate-module").Segment;
const doc = new Docxtemplater(zip, {
    modules: [new SegmentModule()],
});

CHANGELOG

3.11.0

Automatically convert colors that use "accent1", "accent2", …

This means that if your main document and included document have different themeColors, the color used by the output document will be the ones from the main document.

3.10.2

Bugfix to be able to include 3 subtemplates that each contain a chart.

3.10.1

Bugfix when including multiple subtemplates that each have charts.

3.10.0

Add support to include document that contains footnotes or endnotes.

3.9.2

When using the {:include doc} tag from a header or a footer, the section breaks inside of the included documents are dropped.

This was causing a corruption in previous versions.

3.9.1

Correctly change all "basedOn", "next", and "link" styles when including a document.

3.9.0

Make module compatible with docxtemplater@3.28.0. Please make sure to update docxtemplater to 3.28.0 at the same time you update this module. The internal change made is the use of the new matchers API which fixes bugs that were triggered depending on the order of the modules that are attached to the instance. Now the order of the modules should not matter as expected.

3.8.0

Make module compatible with docxtemplater@3.27.0. Please make sure to update docxtemplater to 3.27.0 at the same time you update this module

3.7.1

Bugfix to have the subtemplate work with Office 365 files (files which use word/document2.xml instead of word/document.xml).

The module works in all possible cases now :

  • when the including file is an Office 365 file
  • when the included file is an Office 365 file
  • when using an Office 365 file with the self-including module

3.7.0

Add Subtemplate.Segment module, to allow to define a segment in a document and include it (in the same document).

3.6.7

Use @xmldom/xmldom instead of xmldom, see this github issue

3.6.6

When including a document that has subsections, the header / footer of the main document should be preserved in all cases.

3.6.5

Generate files in built with correct filename In previous versions, the filename was always build/docxtemplater.js. Now the filename is build/subtemplate-module.js The .min.js file is also created now.

3.6.4

Add typescript definitions for public API

3.6.3

Move webpack from dependency to devDependency (which triggered an error during installation on node version 10)

3.6.2

Internal change to allow to match tags with non-breaking space.

When entering Ctrl+Shift+Space, a "non-breaking" space is created.

When using a non-breaking space in the tag {:subtemplate doc}, the tag would not be replaced correctly.

3.6.1

Calculate maxDocPrId lazily (only at the time when we need the value), to avoid overhead when attaching the module.

3.6.0

To better match with the general behavior of docxtemplater, if some subtemplate is null or undefined, nothing will be rendered instead of getting the error : "The subtemplate for the tag 'foobar' does not exist".

This is now the same as with the loop module and the image module for example.

If you give a value that is not null or undefined but is not a valid Docxtemplater document, an error will still be shown.

3.5.6

Continuation of 3.5.5. There was still one case that would throw Cannot read property 'asArrayBuffer' of undefined when using inline images (ones present within a paragraph, inside the content).

The error should no more occur now.

3.5.5

Do not fail with error Cannot read property 'asArrayBuffer' of undefined when having a docx with image (containing absolute Target for images, which might have been generated by some other docxtemplater module or some other program).

Also import correct xmlns attributes from imported document.

3.5.4

Declare supportedFileTypes, which allows to use this module with the new docxtemplater constructor which was introduced in docxtemplater 3.17.

3.5.3

Bugfix "Cannot read property 'appendChild' of undefined" when including a document where the {:include tag} is followed by a page break

3.5.2

Make it possible to have pagebreaks between two includes, without removing the pagebreak.

3.5.1

Fix issue Cannot read property 'getAttribute' of undefined when having unnamed styles in main document.

3.5.0

  • Add numId from styles.xml so that numbering values are better copied

  • Include w:sdt tags in addition of w:p tags

3.4.8

  • Handle numeric style ids by using name for the comparison if the id exists.

3.4.7

  • Fix Memory Leak when including document containing many images.

3.4.6

  • Bugfix : add possibility to include image that is within a table

3.4.5

  • Update browser build to use XMLSerializer instead of xmldom

  • Use requiredAPIVersion

3.4.4

  • Move docxtemplater from devDependencies to dependencies

Explanation : On some versions of npm (notably 5.8.0), when having a package containing docxtemplater-subtemplate-module, the installation will generate a tree of node_modules that puts the module on a level where it has no access to docxtemplater. By explicitly asking it as a dependency, this issue is avoided.

3.4.3

Fix bug when using equations and including templates 2 levels deep (with parent.docx /son.docx and grand-son.docx which contains an equation).

3.4.2

  • Make module compatible with docxtemplater version 3.5 and below.

Explanation : Recently, the scopemananger API (internal API) has changed, this new version of the subtemplate module makes the module work with both versions newer than 3.6 and older than 3.6 of docxtemplater.

3.4.1

Add support for adding arrays of subtemplates with subsections.

When using the SubsectionModule, make it possible to replace the first section of the including document and replace the last section of the included document (this avoids additional pagebreaks).

3.4.0

Add support for adding subsections with headers by using subsection module.

3.3.0

Add possibility to add sections from subdocument if .includeSections is true

3.2.5

Add meta context argument to custom parser with information about the tag for each types of tags

3.2.4

Add support for including documents with pagebreaks

3.2.3

Fix corruption when including equations

3.2.2

Add support for including charts refering to Excel documents

3.2.1

Add support for including documents containing Excel documents (OLEObjects)

3.2.0

Add support for including documents containing comments

3.1.9

Avoid corruption when including multiple charts with subtemplates

3.1.8

Bugfix corruption when including document with chart

3.1.7

Add support for including documents containing charts

3.1.6

Remove error getElementsByTagName when word/numbering.xml doesn't exist in main document

3.1.5

Fix bug when subtemplate contains list coming from an other module (HTML)

3.1.4

Images in the subtemplate when there are already some images in the headers does not cause a corruption anymore.

3.1.3

Links in the subtemplate are now handled correctly

3.1.2

Fix corruption on some word version because of duplicate styles

3.1.1

Add support for lists in subtemplates (ordered lists and unordered lists).

3.1.0

Import styles in the case when the included document defines some styles.

3.0.1

Handle images importing

3.0.0

Initial release