drlaz_1

If the default behavior is buggy, read the big number as a string and create a variable corresponding to its BigDecimal value obtained from the BigDecimal(String) constructor. Then just use the variable.

I have a report in which I'd like to use Unicode flags. You can get a national flag in Unicode by adding a magic constant to each character of the ISO 2-character abbreviation for the country. The result is like an emoji. I do the calculation in the database. For purposes of this question, I've duplicated the formula in the report itself, in the second column. new StringBuilder().append(Character.toChars(127462+$F{country_code}.charAt(0)-'A')).append(Character.toChars(127462+$F{country_code}.charAt(1)-'A')) From the first screenshot, you can see this works great, both the calculated field, and display of the string taken straight from the database (third column). Now I add this font to the list available for PDF export (Preferences menu; probably Settings on Windows). I can name the font extension either the original font name, or a new one; behavior will be the same. You can see in Screenshot 2, this breaks the rendering of the flag from the database. The calculation in the report continues to yield the flag! Jaspersoft bug? I don't even know how this would happen!

I think under Preferences/Java/Compiler/Compiler Compliance Level. I have to say, though, that I can't get Studio to work with my class files compiled for Java 14 with Preview, even by filling this form out.