---

Macro Compatibility

---

Usage

Vertically merge cells (downwards) that have the same data. For a cell to merge down, all previously indexed columns should be identical, not just the immediately previous one. Only the top-most style is retained. The macro assumes a header row which it ignores - however you may set ignoreHeaderRow to false to override. Note: the original table must not contain any existing vertically or horizontally merged cells, or the output of this macro will be unpredictable.

---

Parameter	Type	Presence	Purpose	Options	Default
columnIndices	List<Int32>	Mandatory	The column indices, separated by a semi-colon, to consider for merge. Column 1 is the leftmost column. You can specify them in any order.	N/A	N/A
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
errorOnOverflow	Boolean	Optional	Should NCalc expression evaluation throw error on Overflow	true false	true
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
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
ignoreHeaderRow	Boolean	Optional	Whether to ignore all cells in the header (first) row.	true false	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 object, 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

---

Examples (1)

Example 1:

This example vertically merges cells in columns 1, 2 and 3 that have the same cell value:

[List.Table: values=a^b^c^d^e^f;a^b^c^d^e^f;a^b^c^d^e^f;a^b^c^d^e^f]
[Table.MergeCells: columnIndices=1;2;3]