Working with Outer Document Insertion Leave feedback
NoteThe code uses some of the objects defined in The Business Layer.
You can insert contents of outer documents into your reports dynamically using doc tags. A doc tag denotes a placeholder within a template for a document to be inserted during run-time.
<<doc [document_expression]>>
WarningA doc tag can be used almost anywhere in a template document except text-boxes and charts.
An expression declared within a doc tag is used by the engine to load a document to be inserted during run-time. The expression must return a value of one of the following types:
- A byte array containing document data
- A Stream instance able to read document data
- An instance of the Document class
- A string containing a document URI
WarningIf an expression declared within a doc tag returns a stream object, then the stream is closed by the engine as soon as a corresponding document is loaded.
By default, a document being inserted is not checked against template syntax and is not populated with data. However, you can enable this by using a build switch as follows.
<<doc [document_expression] -build>>
When a build switch is used, the engine treats a document being inserted as a template that can access the following data available at the scope of a corresponding doc tag:
- Data sources
- Variables
- A contextual object (see “Using Contextual Object Member Access” for more information)
- Known external types (see “Setting up Known External Types” for more information)
TipFor detailed technical information about syntax, expressions and report generation by the engine, please visit: Working with GroupDocs.Assembly Engine
Get designed and outer templates from here.
NoteThis feature is supported by version 18.12 or greater.
Get designed and outer templates from here.
NoteThis feature is supported by version 18.12 or greater.
Get designed and outer templates from here.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
