This documentation describes how to use Freemarker edit codes to hide decimals from view, while still allowing it to be used in calculating sub and grand total levels.
Example Scenario
So that you can easily see the difference, a Regular Report application has been built with the dimension key set to the Customer State. Only one numeric field has been selected (Original Field). For comparison purposes, a calculation has been used to replicate this numeric field (Edited Field).
Before any editing is done, my report output looks like this:
Since this requires HTML editing, we must open m-Painter.
Right-click on your field at the detail level, and select “Cell” then “Edit Cell HTML”. Replace ?html} with _o?string("$,##0")}.
Be sure to repeat the process for your field on the sub-total and grand-total rows.
Click the “Save” button & run your application. My output now looks like this:
The Original Field was left unaltered to show the comparison between itself and the HTML edited field.
Other Formatting Options
You can utilize numerous formatting, such as the following. (Assuming the field value is 1.234)
| Freemarker | Output |
|---|---|
| ${FIELD_o?string(“0”)} | 1 |
| ${FIELD_o?string(“0.#”)} | 1.2 |
| ${FIELD_o?string(“0.##”)} | 1.23 |
| ${FIELD_o?string(“0.###”)} | 1.234 |
| ${FIELD_o?string(“0.####”)} | 1.234 |
You can even use this same method for Rounding purposes:
· If value = 1.2, then ${FIELD.string("0")} yields 1.
· If value = 1.8, then ${FIELD.string("0")} yields 2.
· If value = 1.5, then ${FIELD.string("0")} yields 2 (Rounding always goes to nearest even number).
· If value = 2.5, then ${FIELD.string("0")} yields 2 (Rounding always goes to nearest even number).