Skip to main content

Troubleshooting

This page collects reporting problems that occur regularly in ADITO projects and the fixes that have proven useful in practice.

Bold text is missing in exported PDFs​

If text looks correct in the client preview but loses bold or italic styling in the exported PDF, the root cause is usually font configuration, not the text element itself.

Preferred fix:

  • create and deploy a proper Font Extension,
  • use a font with bold and italic variants,
  • ensure the font is embedded for PDF export.

Related page:

Fonts on ADITO Cloud systems​

If a custom font works locally but not on the target system, the font extension JAR must also be available on the server or on every relevant pod in ADITO Cloud.

See:

Convert a millisecond string into a date​

If a field contains a timestamp as a string and you want to display it as a date inside the report:

  • set the text field expression to:
new java.util.Date(Long.parseLong($F{DATEFIELD}))
  • set the expression class to:
java.util.Date
  • optionally guard empty values with a Print When Expression, for example:
$F{DATEFIELD} != ""

Chart axis should show only integers​

For Jasper chart value axes that should display only integer steps, add this property expression:

net.sf.jasperreports.chart.range.axis.integer.unit = true

If zero values lead to an awkward axis rendering, set the range axis minimum explicitly:

Double.parseDouble("0")

Sorting looks like 1, 10, 11, 2​

If a position field is sorted lexicographically instead of numerically:

  1. Inspect the report definition for an unwanted sortField entry.
  2. Remove it if the underlying JDito data is already sorted correctly.
  3. If necessary, sort the data before handing it to the report.

This problem often appears in quotation or line-item style reports.

Report seems to load forever​

A common cause is a subreport overflow combined with an incompatible text field configuration.

Problematic combination:

  • Stretch with Overflow
  • Position Type = Fix relative to Bottom

Recommended fix:

  • set Position Type to Fix relative to Top

This avoids recursive or unstable layout expansion in the subreport.

Deleted subreports still cause errors​

Sometimes a deleted subreport leaves dead references behind in the report metadata.

If the report still fails after removing the subreport in the Designer:

  1. Inspect the report directory and remove obsolete .jrxml files if they still exist.
  2. Open the report's .aod file.
  3. Remove dead <subreport> references that still point to deleted files.

Do this carefully and preferably under version control so the cleanup stays reviewable.

Subreport shows too many rows​

If every master row renders all child rows, the subreport is missing the correct relation filter.

Check that:

  • the master report passes the current key as a subreport parameter,
  • the subreport declares the same parameter,
  • the subreport Filter Expression compares parameter and field correctly.

Typical expression:

$P{FILTER_CONTACTID}.equals($F{CONTACTID})

More help​

If the issue is layout- or engine-specific rather than ADITO-specific, continue with: