ReportMagic

[EmailReport:]UPDATED

Emails the entire completed report once complete.

Compatibility

The macro can be used in the highlighted input document types only. A greyed-out icon indicates not supported.

Usage

The [EmailReport:] macro can be used to email a completed report as an attachment (in docx, pdf, xlsx or pptx formats). The macro can be placed anywhere in a document, and will be removed in completed reports. Any email address used may include an optional display name, in which case the email address (person@domain) must be specified inside angle brackets, e.g. Bob Smith <bob.smith@mycompany.com>. Note that the validity and structure of email addresses are not validated. It is up to the macro user to ensure well-formed addresses are used. Whitespace is ignored. For Production (i.e. not free) reports, if none of the attach_xxx parameters are set, a Docx file WILL be selected. Note: when using the attach_xxx parameters, it is very important to ensure the Schedule has the correct output format selected. The email will be sent regardless, but may be missing attachments if the Schedule's output formats do not match the options chosen here.

Updates

v4.4One month ago · July 2026

Added the 'sendIfContainsErrors' parameter to suppress sending the email if the report contains any errors.

History (1)

One year ago · April 2025

Added the 'compressFiles' parameter to allow the output files to be sent as .zip files.

Parameters (29)

Grouped View

Mandatory (2)

Parameter	Type	Purpose	Options	Default
subject	String	The e-mail subject.	N/A	N/A
to	List<String>	A semicolon-separated list of e-mail addresses.	N/A	N/A

Behaviour (2)8 additional

Parameter	Type	Presence	Purpose	Options	Default
hidden	Boolean	Optional	Whether the section of the Word document contained inside the macro should be removed in the final output document (does not affect e-mail content).	true false	false
sendIfContainsErrors	Boolean	Optional	Whether the e-mail should still be sent if any macro error or system error occurs. For the [Email:] / [EndEmail:] macros this applies to errors within the section between them; for the [EmailReport:] and [EmailFile:] macros it applies to any error anywhere in the report. Set this to 'false' to suppress the e-mail when such an error occurs (for [Email:] sections the content is still included in the output document unless 'hidden' is also set). Defaults to 'true'.	true false	true

Additional (8)

Parameter	Type	Presence	Purpose	Options	Default
desiredExecutionResult	List<ExecutionResult>	Optional	If specified, asserts the expected execution result of the macro. Accepts a single value or a semicolon-separated list of acceptable values (e.g. 'Success;Warning'). The macro executes normally; if the actual result matches any of the desired values, the result is converted to Success. If the actual result does not match, the result is converted to MacroError with a descriptive message. This is primarily used for testing and diagnostic purposes. Valid values are: 'Unknown', 'Success', 'MacroError', 'WorkerStopped', 'Running', 'Warning', 'NeverRun', 'Cancelled', 'Pending', 'Paused', 'SystemError', 'Deferred' and 'Stopped'.	Cancelled Deferred MacroError NeverRun Paused Pending Running Stopped Success SystemError Warning WorkerStopped	N/A
errorOnOverflow	Boolean	Optional	Should NCalc expression evaluation throw error on Overflow	true false	true
expectedType	String	Optional	If specified, asserts the expected output type of the macro result. The macro executes normally; if the actual type does not match, a macro error is generated. Requires 'storeAs', 'storeAsHidden', or 'storeFormattedValueAs' to be set for typed validation. Valid types include CLR names (e.g. Int32, Int64, Single, Double, Boolean, String, JArray, JObject) and C# keyword aliases (e.g. int, long, float, double, bool, string, uint, ulong, short, ushort, byte, sbyte, decimal, char, object). The special value 'Number' matches any numeric type.	N/A	N/A
expectedValue	String	Optional	If specified, asserts the expected output value of the macro result. The macro executes normally; if the actual value does not match, a macro error is generated. When 'storeAs' or 'storeAsHidden' is set, the stored variable value is compared. Otherwise, the document output text is compared.	N/A	N/A
if	String	Optional	The condition that must be true in order for the macro to be executed/evaluated. Must either evaluate to true or false, for example: "3+5=8" or "contains('abcd', 'z').	N/A	true
mode	MacroMode	Optional	The mode in which variables are stored. In the legacy mode (default for Schedules), the variable created is a string and formatted. In the normal mode (default for Report Studio), the output variable is stored as a strongly-typed theObject, e.g. an Int32 or a List etc., rather than a formatted string.	Legacy Normal	Legacy
obfuscation	ObfuscationType	Optional	Obfuscation type. Use obfuscation to write reports where sensitive data is hidden. When used, ReportMagic guarantees that the same input string will map to the same output string for the whole of the report (but the next time the report runs, it will most likely map to a different value). If you use obfuscation, the property in your macro will not show up and instead, you will see a fake item of the obfuscation type chosen.	None UkTown DeviceName Company IpAddress PrivateIpAddress	None
warning	String	Optional	If specified, adds a warning message for this macro. This is processed as an NCalc, and the warning message will ALWAYS be present and will be the value of the evaluated NCalc expression.	N/A	N/A

Output (6)2 additional

Parameter	Type	Presence	Purpose	Options	Default
attachDocx	Boolean	Optional	Whether to attach the report as DOCX format.	true false	false
attachHtml	Boolean	Optional	Whether to attach the report as HTML format.	true false	false
attachPdf	Boolean	Optional	Whether to attach the report as PDF format.	true false	false
attachPptx	Boolean	Optional	Whether to attach the report as PPTX format.	true false	false
attachXlsx	Boolean	Optional	Whether to attach the report as XLSX format.	true false	false
compressFiles	Boolean	Optional	Whether to send each attachment as an individual .zip (compressed) file. Each .zip file will retain the original filename and add the .zip suffix, e.g. 'My Report.docx.zip'.	true false	false

Additional (2)

Parameter	Type	Presence	Purpose	Options	Default
failureText	String	Optional	The text to display should the macro fail to execute. Note that a poorly-specified macro (e.g. omitting mandatory parameters) will still result in an error message.	N/A	N/A
failureVariable	String	Optional	The name of a variable to create should the macro fail to execute. The variable will be a text variable, and will contain either the failure text (only if the failureText parameter is set), otherwise it will contain the exception / failure message.	N/A	N/A

General (9)2 additional

Parameter	Type	Presence	Purpose	Options	Default
subject	String	Mandatory	The e-mail subject.	N/A	N/A
to	List<String>	Mandatory	A semicolon-separated list of e-mail addresses.	N/A	N/A
bcc	List<String>	Optional	A semicolon-separated list of e-mail addresses.	N/A	N/A
body	String	Optional	The email body text. This will never appear in the actual report, just in the email. Format this as HTML. For the [EmailReport:] macro, this is the entire body. For the [Email:] macro, this is used to prefix the content between the [Email:] and [EndEmail:] macros.	N/A	N/A
cc	List<String>	Optional	A semicolon-separated list of e-mail addresses.	N/A	N/A
displayName	String	Optional	The optional display name (shown in your email application) of the sender. NOTE: you can ONLY change the display name when you have specified a Connection e.g. with the 'connectionName' parameter or in the Configuration JSON section of the Connection. Otherwise email sending uses ReportMagic's default SMTP client and the display name is set by the system.	N/A	N/A
fileSizeTooBigText	String	Optional	The text to send in the email if the attachments are too large to send.	N/A	N/A
from	String	Optional	A single e-mail address. This may not be supported by your email server (i.e. setting the sender to an arbitrary email), and can be omitted to use the default. When the email server does NOT support this, you may receive a System Error when processing the report, so you should check first by testing the macro. NOTE: you can ONLY change the from address when you have specified a Connection e.g. with the 'connectionName' parameter or in the Configuration JSON section of the Connection. Otherwise email sending uses ReportMagic's default SMTP client and the from address is set by the system. In other words, if you set the from address, you must set a Connection, and the email address does NOT need to have been set up anywhere else (you can choose any email but your mail server may not support it).	N/A	N/A
priority	String	Optional	The e-mail priority.	normal high low	normal

Additional (2)

Parameter	Type	Presence	Purpose	Options	Default
comment	String	Optional	Add a comment to make your document template more readable. The comment is discarded in the output document.	N/A	N/A
connectionName	String	Optional	The name of the Connection.	N/A	N/A

Examples (6)

Example 1

A basic example to attach the output document as a .pdf file:

[EmailReport: subject=Completed Reports Attached, to=bob.smith@mycompany.com, priority=high, attachDocx=false, attachPdf=true]

Example 2

This example attaches two output documents (in this case .docx and .pdf) but sends each one as a compressed .zip file:

[EmailReport: subject=New Bat-Mobile Designs Attached, to=bruce.wayne@gotham.com, priority=high, compressFiles=true, attachDocx=true, attachPdf=true]

Example 3

Send an email based on the 'if' parameter:

[EmailReport: subject=Completed Reports Attached, to=bob.smith@mycompany.com, priority=high, attachDocx=false, attachPdf=true, if=`1 < 3`]

Example 4

An example using HTML 'BR' tags (line break) and double quotes:

[EmailReport: subject=example 3, to=alfred.pennyworth@gotham.com, priority=high, attachDocx=false, attachPdf=true, body="Hi Alfred, <br/>Here are the details of this month's capers.<br/>Best Wishes,<br/>Bruce."]

Example 5

An example using HTML 'BR' tags (line break) and back-ticks:

[EmailReport: subject=example 3, to=clark.kent@metropolis.com, priority=high, attachDocx=false, attachPdf=true, body=`Hi Clark, <br/>Here are the details of your next assignment.<br/>Best Wishes,<br/>Lois.`]

Example 6

Only send the completed report if it contains no errors, using 'sendIfContainsErrors':

[EmailReport: subject=Completed Reports Attached, to=bob.smith@mycompany.com, attachPdf=true, sendIfContainsErrors=false]

Compatibility

Usage

Updates

Examples (6)

Example 1

Example 2

Example 3

Example 4

Example 5

Example 6

Search

Reconnection

Reconnection

Reconnection