| New Features |
|---|
| 1. | The RowNumber() function for dashboards. It returns the row number (1..N) of a row in the final sorted result.V2026.4.1 |
| 2. | The "Sankey" chart type in reports and dashboards. It shows the flows between categories as links whose width is proportional to the flow value.V2026.4.1 |
| 3. | The MS SQL data adapter based on the Microsoft.Data.SqlClient provider, which supports strict SQL Server encryption (Encrypt=Strict). It works only on .NET Framework. To use it, create a standard "MS SQL" connection, then select "Microsoft.Data.SqlClient" for the "MS SQL Data Adapter" option on the "Data" page of the report designer options, or set the StiOptions.Dictionary.UseMicrosoftDataSqlClient property to true. The report designer downloads the provider from NuGet.V2026.4.1 |
| 4. | Sparkline in Cross-Tab and Pivot Table.V2026.4.1 |
| 5. | Added the ability to set the color of chart points from a data column in dashboards. It works for the "Pie", "Pie 3D", "Doughnut", "Funnel", "Treemap", "Sunburst" and "Pareto" chart types, as well as for clustered column and bar charts.V2026.4.1 |
| 6. | Support for searching by several terms separated by spaces in the search box of the "ListBox" and "ComboBox" dashboard elements in the web viewer. A phrase enclosed in double quotes is matched as a single term.V2026.4.1 |
| 7. | MonthYear, QuarterYear, WeekYear and DayMonthYear functions in reports and dashboards. They group data by the month, the quarter, the week or the day within the year, keeping the chronological order.V2026.4.1 |
| 8. | The "Report Checker" now checks the expressions of the dashboard elements, including the tool tip, the hyperlink and the parameter values of the interaction, and reports unknown functions, missing data columns and broken expressions in filters and conditions.V2026.4.1 |
| 9. | The PrimaryKey property has been added to the data columns in the data dictionary. The key columns are taken from the data source schema or from the Key attribute of business objects, shown with a key icon in the dictionary tree, and preselected when creating a relation in the report designer.V2026.4.1 |
| 10. | The relations of the data dictionary are now created from the foreign keys of the database when retrieving columns from a SQL connection of any type: MS SQL, MySQL and MariaDB, PostgreSQL, Oracle, Firebird, SQLite, SQL CE, Access, Teradata, Snowflake, DuckDB, VistaDB, as well as the connections through ODBC and OLE DB.V2026.4.1 |
| Enhancements |
|---|
| 1. | Support for VistaDB 6 databases: the VistaDB connection now works through the VistaDB 6 provider, databases of VistaDB 5 are still opened, and the primary keys of the tables are retrieved.V2026.4.1 |
| 2. | XLS files in the Excel data source are now read by the built-in reader on all platforms. LibExcel is no longer downloaded and is used only if installed. XLS columns now get data types as in XLSX, the UseLibExcelCompatibleTypes option restores text columns.V2026.4.2 |
| 3. | Region names in the data are now also found in the other languages of the map in the "Map" report component and the "Region Map" dashboard element. For example, "Bayern" or "Thüringen" in the data now color their regions on the Germany map shown in English.V2026.4.2 |
| 4. | Region names in the data are now also found when they are written without accents or punctuation, for example "Bourgogne-Franche-Comte" or "Provence-Alpes-Cote d'Azur", in the "Map" report component and the "Region Map" dashboard element.V2026.4.2 |
| 5. | The error of a broken expression of a dashboard element is now displayed on the element itself in the report designer and in the rendering messages of a report. Before, such an error was skipped silently and the element just showed no data.V2026.4.1 |
| 6. | Retrieving the database schema of an Informix connection in the report designer, including tables, views, columns, stored procedures with parameters and relations.V2026.4.1 |
| 7. | Retrieving the database schema through an ODBC driver has been reworked: the primary keys and the relations are retrieved, and the system objects are no longer listed among the tables.V2026.4.1 |
| Fixed Bugs |
|---|
| 1. | No rows in the "View Data" window and in the report for the tables of a Teradata or VistaDB connection created from the database schema in the report designer.V2026.4.1 |
| 2. | Synchronizing the columns and the primary keys of the data sources of an OData V1-V3 connection with the "Synchronize" command of the data dictionary. These data sources were skipped: their columns were not updated, and a primary key unchecked in a column did not come back.V2026.4.1 |
| 3. | Retrieving the types of the columns which an ODBC driver names in its own way when reading the database schema: int4, float8 and timestamptz of PostgreSQL, DOUBLE PRECISION of Firebird, datetime2 and the identity columns of MS SQL. Such columns came as strings, the tables with a space in the name came without columns, and the relations of these tables and key columns were lost in the data dictionary.V2026.4.1 |
| 4. | The data sources added through an ODBC driver failed to build in a report when the name of a table, a view or a stored procedure contained a space or mixed-case letters, or when the table belonged to a schema: the names in the query were quoted the wrong way for the database, and the schema was added twice.V2026.4.1 |
| 5. | Displaying the views of an Oracle database in the "Select Data" form when connecting through the Devart provider.V2026.4.1 |
| 6. | Large integer values were lost when loading JSON data into reports and dashboards.V2026.4.2 |
| 7. | Numeric values could lose precision when loading JSON data into reports and dashboards.V2026.4.2 |
| 8. | Nested JSON rows could be linked to the wrong parent after an empty array when loading data into reports and dashboards.V2026.4.2 |
| 9. | Reading numeric strings from JSON data depended on the current culture, and invalid values could be replaced with zero in reports and dashboards.V2026.4.2 |
| 10. | Preserving null values and empty numeric strings in nullable data columns when CastToColumnType is enabled in reports and dashboards.V2026.4.2 |
| 11. | Fixed slow loading of reports and dashboards with fonts that are not installed on the system.V2026.4.2 |
| 12. | Wrapping a one-character word that did not fit at the end of a line in a text component using the SixLabors library: the component did not grow to accommodate the extra line, and the last character was clipped.V2026.4.1 |
| 13. | Using the server cache in the web viewer and the web designer when several requests are processed at the same time. A request could use the session of another request or replace newer cached data with older data.V2026.4.2 |
| 14. | Loading JSON data with numbers in exponential notation (for example, 6.9E-07) into reports and dashboards. Previously, all tables of such a data source were empty.V2026.4.2 |
| 15. | Displaying Bavaria and Hesse on the Germany map in the "Map" report component and the "Region Map" dashboard element. Most of Bavaria was drawn in gray over an outdated outline that overlapped Baden-Württemberg, and data with the English name "Hesse" did not reach the region.V2026.4.2 |
| 16. | Displaying maps when several of them are loaded at the same time, for example in a dashboard with several "Region Map" elements. A map could be shown in English instead of the selected language, not drawn at all, or fail with an error.V2026.4.2 |
| 17. | Using the official ISO codes of the regions, for example "FR-ARA", on the "France" and "France (18 Regions)" maps in the "Map" report component and the "Region Map" dashboard element. Codes without the country prefix are still recognized, and the English and French region names of both maps have been corrected.V2026.4.2 |
| 18. | Fixed an issue where the "Button" dashboard element was exported with a white background instead of the colors of its style.V2026.4.2 |
| 19. | Fixed an issue where a round "Button" dashboard element was exported as a rectangle instead of a circle.V2026.4.2 |
| 20. | Fixed an issue where the icon of the "Button" dashboard element was exported smaller than it is shown in the viewer.V2026.4.2 |
| 21. | Fixed an issue where semi-transparent backgrounds of dashboard elements, such as indicators and charts, came out lighter when exporting a dashboard.V2026.4.2 |
| 22. | Fixed an issue where texts in the "Fit" size mode came out smaller and combo boxes cut their text when exporting dashboard elements with rounded corners.V2026.4.2 |
| 23. | Exporting rotated text in SVG images to PDF. Such text lost its rotation and was drawn horizontally.V2026.4.2 |
| 24. | An issue where the editors of dashboard elements reported the Variable.Label expression as not found in the data dictionary has been fixed.V2026.4.2 |
| 25. | Fixed issues with the "Button" dashboard element: its icons were exported to SVG and HTML as empty squares and came out too large on screens with display scaling, and the border of a round button was cut at the top and bottom in the dashboard viewer on such screens.V2026.4.2 |
| 26. | An issue where the editors of dashboard elements reported an error in the expressions with variables named in Chinese or other non-Latin letters has been fixed.V2026.4.2 |
| 27. | Security vulnerabilities in image processing for .NET Core products have been fixed.V2026.4.2 |
| 28. | The "Interaction" editor of the dashboard elements reports a broken expression right under the field which holds it - the tooltip, the hyperlink or the value of the parameter.V2026.4.1 |
| 29. | The data type of the FLOAT and SMALLFLOAT columns of an Informix data source, FLOAT is now double precision and SMALLFLOAT is single precision.V2026.4.1 |
| 30. | Missing string columns in the schema of an OData V1-V3 connection in the report designer when the properties are marked as nullable in the service metadata.V2026.4.1 |
| 31. | Connecting to an IBM DB2 database with the installed IBM Data Server Driver in the report designer; the "DB2" connection is available again in the list of data sources.V2026.4.1 |
| 32. | Positioning of underline and strikeout lines for text drawn with synthesized fonts when exporting a report to PDF.V2026.4.1 |
| 33. | Losing the version of an OData connection when saving a report to an *.mrt file with JSON markup or previewing it in the report designer. A connection configured for OData V1-V3 was treated as V4, and the data source remained empty.V2026.4.1 |
| 34. | Saving the connection parameters of a Google Sheets data source when saving a report to an *.mrt file with JSON markup.V2026.4.1 |
| 35. | Saving the code page of a dBase data source when saving a report to an *.mrt file with JSON markup.V2026.4.1 |
| 36. | Exporting data of the "Table" dashboard element to Data formats. Unnecessary columns could appear in the exported file, and column headers were missing for CSV, DIF and SYLK.V2026.4.2 |
| 37. | Retrieving the database schema through the Oracle ODBC driver no longer crashes the report designer. The columns of the whole database were requested from the driver at once, and it brought the process down; now they are read schema by schema.V2026.4.1 |
