Stimulsoft Dashboards.BLAZOR 2025.4.3

Veröffentlicht am 12. November 2025
Neue Möglichkeiten
1.Added new "3D Area" chart type in reports and dashboards.
V2025.4.1
2.Added new "Surface" chart type in reports and dashboards.
V2025.4.1
3.Ability to change column widths in the "Table" dashboard element.
V2025.4.1
4.The operation “Equal to variable or variable is null” in string-type filters on the “Data” band.
V2025.4.3
5.New SubTotal(,) function for the “Pivot Table” dashboard element.
V2025.4.3
6.Added a new action "Running Average" to "Data Transformation".
V2025.4.1

Verbesserungen
1.Report deserialization improvement - if an enum type value does not exist, the default value of that enum type will be deserialized. This is done to resolve certain issues that happen when reports created in newer versions of the designer are opened in older versions of the designer.
V2025.4.1
2.Support for the legacy .NET Core 3.1 framework has been removed. We strongly recommend upgrading to the newer versions .NET 6.0 or .NET 8.0. If necessary, a source code license allows you to compile components for legacy frameworks.
V2025.4.1

Behobene Fehler
1.Error using variables of type "Range" when viewing a report in the viewer.
V2025.4.1
2.A problem with some numeric ranges which are used as parameters has been solved.
V2025.4.1
3.Incorrect scaling for the "Indicator" element when exporting a dashboard.
V2025.4.1
4.The RuntimeInstanceNotAllowed error occurred when using some report components in a published Blazor Wasm .NET 9.0 project.
V2025.4.1
5.Displays the selected font in the font list.
V2025.4.2
6.A problem with parsing types with System alias has been fixed.
V2025.4.3
7.Some issues with parsing types during array creation have been fixed.
V2025.4.3
8.Filling in the parameter type when retrieving columns from an Access data source.
V2025.4.3
9.Handling special characters in SQL queries for various data sources.
V2025.4.3
10.Processing JSON data in cases where a field can contain values of different types.
V2025.4.3
11.Nullable type conversion for the data source has been fixed.
V2025.4.3
12.An issue with filtering data in interpretation mode related to incorrect string parsing has been fixed.
V2025.4.3


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.