PDF export:
Sub-reports containing images, were sometimes not included in the created PDF file.
If the property 'Replace Missing Characters' was enabled, then sub-reports were sometimes not included in the created PDF file.
IllegalArgumentException sometimes occurred during the creation of a signed PDF file.
Unicode characters, containing some special byte values(0x28,0x29,0x5c), could not be displayed correctly in the bookmarks of the PDF file.
Borders and shadows of elements painted into the next section.
Position of a hyperlink in the PDF file was incorrect, if the hyperlink was created using a field with text interpretation “HTML (advanced)”.
The hierarchy of bookmarks was lost in the exported PDF file.
Pictures encoded as BMP with BitFields and 16bpp (ARGB) has been displayed incorrectly in the exported PDF file.
Fields with text interpretation “HTML(advanced)” were not displayed if the property “Suppress if Duplicated” was enabled.
Sometimes cache was hanging for 15 minutes after refresh button in Java report viewer was clicked, if embedded fonts were used.
N-datatypes of JDBC 4 (e.g. NClob) not supported, if Java 6 was used.
Translations in the report was not used for parameter fields (prompts) and formulas.
Sometimes error message has not occurred in case a basic formula did not assign the 'formula' variable.
Image export: The export of on-demand sub-reports has produced corrupt image files.
Borders and shadows of elements painted sometimes into the next section.
In rare cases an extra empty line in text fields including field parts and empty lines occurred.
For elements using basic HTML interpretation, justified bullet lists were not justified in the first line
RTF export: Not transparent images were not displayed in OpenOffice writer.
The “on demand” sub-report label formulas were not correctly read by the Report Reader tool.
A vertical line or box from the page header to group footer section was not drawn on a page, if it was the group footer of the last record, the group footer was on the top of the next page and there was no group footer on the current page.
The methods RDC.loadEngine(File file) and RDC.loadEngine(File file, xxx) could not read report templates that was saved as directory.
A line or box from the page header section to a group footer section was not painted, if it was the group footer of the last record and the group footer was displayed on a top of a new page (after page header).
Column for identical groups was added multiple times to the OrderBy statement.
When opening a report with two data sources, of which one was already registered as a data source configuration and the other was not, settings from the second data source could overwrite settings from the first.
HTML prompt request dialog: Property “Default values only” was not used.
The height of a section was increased to the default cross-tab height, if the section contains a very small cross-tab (smaller than the cross-tab default height) and if the height of the section was smaller than the default cross-tab height.
The character # was not quoted, if report was executed on a MySQL database.
Excel Export:
If the first group is invisible and the group header in the second group is suppressed and the group footer in the second group contains some data, the new sheets pro first group have not been created.
Text strings was formatted with STANDARD-Format instead of TEXT-Format. Therefore numbers and dates, that are written as text, was shown in Open Office with an apostrophe as first character.
No column was added to the XLS file for thin report elements (<3mm).
The height of a section was increased to the default crosstab height, if the section contains a very small crosstab (smaller than the crosstab default height) and if the height of the section was smaller than the default crosstab height.
Because of a bug in the Java VM on the Mac OS, a security exception occurred if a not privileged user tries to use user preferences and i-net Crystal-Clear internally tries to use the System preferences.
ArrayIndexOutOfBoundsException in the translator occurred if the same placeholder, e.g. {0}, was used multiple times within the same string.
Fields in the subreport were not displayed, if the property “Suppress if Duplicated” was activated and the text interpretation “Html (advanced)” was used.
The text property “Manual Formatting” was not working correctly in many cases, if it was used for crosstab fields.
HTML export:
Fields with text interpretation “HTML(advanced)” were not displayed if the property “Suppress if Duplicated” was enabled.
The property “Manual Formatting”, category “Text”, was not work in in many cases for fields in a crosstab.
If there were SQL expression fields in the report and the report's data sources were converted to a single SQL command, the expression fields were removed from the report. Now they are instead turned into database fields based on the column in the SQL statement named the same as the SQL expression field was named.
If a report file from an older version of i-net Crystal-Clear was based on a query file and the query file could not be found, the report file was unable to be read.
Characters in Crystal Reports templates such as 0x01 which are illegal for XML 1.0 files caused reports to not be able to be converted correctly. These characters are now converted to white spaces instead.
Summary functions in formulas, which have a number-array as parameter have null returned instead of 0 for empty or not initialized arrays.
Any URL parameters manually after the UID parameter which the HTML prompt dialog created were truncated.
