The use of the "?string" option is vital. Numeric values such as 1000000 are easy for a computer to understand, but difficult for a human because the zeros run together. However, written like 1,000,000 is very easy for a human to read. Similarly, if a value is smaller than 1E-16 (a number with more than 16 positions to the right of the decimal place) it would be rounded to zero, whereas a string function would display the true value. Converting this value to a string allows the JVM installed to control the look of the value based upon the location. European JVMs could render a value formatting slightly different than a US JVM due to the location.<\/p>\n
As an example, let's say that I have a field with a value equal to 1234. If no Edit Code is selected within m-Power, my output will look like this:<\/p>\n
![](\"\/legacy\/images\/freemarkernumbers1.jpg\")
<\/p>\n
Next, I will illustrate the two most popular Freemarker Formatting options: Number & Currency:<\/p>\n
My normal field substitution looks like this:<\/p>\n
_o<\/strong> — This specifies to Freemarker that this is a numeric field, capable of allowing string manipulation.<\/p>\n string.number<\/strong> — This specifies to treat this field like a normal, numeric field (Using commas and periods where necessary).<\/p>\n string.currency<\/strong> — This specifies to treat this field to display like money (The use of $, commas and period where necessary).<\/p>\n Note:<\/strong> If you are located outside of the US, your string.number and string.currency will display differently as your JVM is written specifically for your country's standards.<\/p>\n${row.OTHERSS?html}<\/code> — This outputs the text 1234 (This is the default code generated by m-Power).<\/p>\n${row.OTHERSS_o?string.number}<\/code> — This outputs the text 1,234.<\/p>\n${row.OTHERSS_o?string.currency}<\/code> — This outputs the text $1,234.00.<\/p>\n![](\"\/legacy\/images\/freemarkernumbers2.jpg\")
<\/p>\n