Multi Line Expressions
Multiple lines of text can be produced in a report by a
single expression. To create a multi-line expression, insert a line feed before
any new line. To do this, press the Enter key at the appropriate place in the
code editor. There is no limit to the number of lines that can be included. For
example, if you enter the following expression:
Number:
{5 + 2}
After the calculation, the result appearing in the report:
Number:
7
The text output has two lines, one atop another.
An expression can contain any number of lines.
Code in Multi-Line
Expressions
There are no additional limitations on using code to
calculate values in multi-line expressions, other than those for Single-line
expressions.
Related Articles
Creating Multi-Column Reports in Report Designer
The articles in this section of the Knowledge Base involve working with Columns for display in your reports. To access the Report Designer, select Toolbox Setup > Design Reports > Design (Report Type) Report. Select New Report to design a report from ...Text Expressions
Text expressions are the simplest expressions. Here are some examples: SampleText 54321 Example All of the expressions above are strings, and there are no calculations. These expressions would be printed as they have been defined. These types of ...Conditional Expressions
Conditional Expressions are not permitted. Conditional behavior can be forced, when necessary, in two different ways. IIF Function {IIF(Condtion, ValueA, ValueB} In the above calculation, the “Condition” is tested to determine if it evaluates ...Using Expressions in the Rich Text Editor of Report Designer
The articles in this section of the Knowledge Base involve working with Rich Text for display in your reports. To learn more about the Rich Text editor, and how to access this section within the Report Designer, see An Introduction to the Rich Text ...Using Functions in Expressions
Built-in Functions There is a variety of built-in functions available in the Report Designer. These functions can be accessed directly from the data dictionary, or from within the Expression Editor. Here is an example of a built-in function: ...
Recent Articles
Toolbox Release Notes | Build 24.1.1105.641
The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...Microvellum Foundation Library Release Notes | Build 24.1025
The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...Toolbox Release Notes | Build 24.1.1030.641
The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...Toolbox Release Notes | Build 24.1.1010.641
The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...Toolbox Release Notes | Build 24.1.1001.641
The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...