Neue Möglichkeiten
1.The StiOptions.Engine.Maps.DisabledMaps property allows you to exclude maps from the Map report component and the Region Map dashboard element.
V2026.1.5
2.Added support for the "try", "catch" and "finally" keywords in the parser.
V2026.1.1
3.Added a new Amazon Redshift data source.
V2026.1.1
4.Added support for writing literals using "uNNNN" syntax in expressions.
V2026.1.1
5.Added support for parameters in queries to a BigQuery data source.
V2026.1.1

Verbesserungen
1.The compilation error message now includes the line/column number and error code.
V2026.1.5
2.Improved the use of the Indent property for the Hierarchical band.
V2026.1.1
3.Eliminated duplicate images: images are now added to report resources once, and report components only reference them.
V2026.1.1
4.Improved updating of the selected component's properties in the properties panel when navigating components with the Left, Top, Right and Bottom buttons in the report designer.
V2026.1.1
5.Optimized moving a large number of components on a page in the WPF report designer.
V2026.1.1

Behobene Fehler
1.Fixed incorrect saving of the default Watermark.TextBrush value to JSON format.
V2026.1.3
2.Fixed processing the "Diameter" property for a "Pie" chart type.
V2026.1.4
3.Fixed processing decimal64 data in a ClickHouse data source.
V2026.1.5
4.Improved the algorithm for detecting whether a font style needs to be synthesized when exporting a report to PDF.
V2026.1.5
5.Fixed attached files being incorrectly allowed in PDF/A-1 mode when exporting a report to PDF (per specification).
V2026.1.5
6.Fixed line spacing when displaying HTML tags in the WPF report generator.
V2026.1.5
7.Added functions RuntimeType(), RuntimeName(), RuntimeVersion(), RuntimeIdentifier(), RuntimeOS() to determine the current execution environment.
V2026.1.5
8.Fixed displaying zero values in a "Heatmap" chart.
V2026.1.6
9.Fixed processing of the "OpenStreetMap" (OSM) provider in online maps.
V2026.1.7
10.Fixed incorrect line-height calculation when exporting to PDF for fonts with incorrectly set Ascend/Descend parameters.
V2026.1.7
11.Fixed incorrect indentation for nested list items when exporting to HTML.
V2026.1.7
12.Fixed numeric parameters not being converted to string when parsing an SQL command with the "en-US" culture set.
V2026.1.7
13.Fixed the <p> tag inside a <li> tag creating an extra line in the HTML tags engine.
V2026.1.7
14.Fixed the positioning of subscript text in the HTML tags engine.
V2026.1.7
15.Fixed several security issues in the C# parser.
V2026.1.1
16.Fixed abstract array types not being supported in the C# parser.
V2026.1.1
17.Fixed excluding a data source from the GUI in the report designer, and retrieving data from that source.
V2026.1.1
18.Fixed dragging and dropping components in the Report Tree panel.
V2026.1.1
19.Fixed text formatting for List and Range variables of the DateTime data type.
V2026.1.1
20.Fixed using variables as arguments in queries to a GraphQL data source.
V2026.1.1
21.An issue with the default checked state of the binding items in the report variables has been fixed.
V2026.1.1
22.Fixed connections to data sources not stopping when the "Request Parameters" property is set to "True".
V2026.1.2
23.Fixed an error that occurred when reopening the Image component editor in the WPF V2 report designer.
V2026.1.2
24.Fixed the length of the password input field when opening an encrypted *.mrx report template in the WPF V2 report designer.
V2026.1.2
25.Fixed a rare infinite loop in EngineV2 when the "Print At Bottom" property is enabled in the "Sub-report" component.
V2026.1.2
26.Fixed the background of the "Shape" component not exporting correctly to MS Word.
V2026.1.2
27.Fixed the output of zero values in the ToWordsZh() function.
V2026.1.2
28.Fixed the JoinColumnContent() function for business objects not working correctly with calculated columns.
V2026.1.2


By using this website, you agree to the use of cookies for analytics and personalized content. Cookies store useful information on your computer to help us improve efficiency and usability. For more information, please read the privacy policy and cookie policy.