Improves exporting to DOCX and PDF.
Fixes
- A report is exported with the DXXRDV name if the DisplayName property contains an apostrophe mark
- A spanned cell is shown in the PageHeader band whose PrintOn property is set to NotWithReportFooter and the ReportFooter band is shown on the same page
- A wrapped rotated string is cut off when a report is exported to PDF
- ASPxDocumentViewer - Print Report button does not work after Google Chrome Update 76.0.3809.132
- Binding Expressions with a multi-value report parameter do not work
- DevExpress.Data.Filtering.Exceptions.InvalidPropertyPathException is thrown on showing a report with a chart whose series has two data filters and the Series. DataFiltersConjunctionMode property is set to OR
- Document Viewer - Interactive functionality doesn't work if at least one brick is selected
- DocumentPreviewControl - System.NullReferenceException is thrown when showing the control in a specific scenario
- End-User Report Designer - The (none) option is not shown for a cascading parameter (AllowNull = True)
- EUD - Script's Page: Control and Event ComboBoxes are empty
- Export to DOCX - Formatted text loses underlines if they are split across document pages
- Export to DOCX - Large images or charts may be split between document pages incorrectly in "SingleFilePageByPage" export mode when the "TableLayout" option is enabled
- Export to PDF - GDI handles leaks under a certain XtraReport layout configuration (text boxes in XRRichText)
- Invalid value conversion error for the "Point-Fixed positive" editor
- Issue with double clicking the FieldList item in combination with a custom FieldListNodeTool
- Report Parameters - A calculated field cannot be used for sorting dynamic look-up collections (the "Invalid Data Member" error)
- Report Summary - Changing TextFormatString in the BeforePrint event handler does not work
- Search doesn't work for the filed list in the XRPivotGrid Designer
- Visual Studio Report Designer - External REPSS styles do not work at the inherited report level
- Web Reporting - The 'Request is not available in this context' error occurs on loading a report layout