Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Weekly release
Main release
Bold Reports can now be configured with Amazon S3 storage in the same way as the existing file and blob storage backends, so teams already standardized on S3 can keep report definitions, exports, and assets in their own bucket without introducing a second storage platform.
All email activity logs can now be viewed inside Bold Reports itself, letting administrators confirm whether a scheduled delivery or notification was sent without opening the mail server or a separate log store.
A server auth token can now be obtained by validating a user’s OAuth token, so embedded applications can reuse the identity they already hold instead of managing a separate credential.
The Cascading parameter API was extended to return the cascading sub parameters of main parameters, giving embedders full visibility into a parameter’s dependent values through the API.
The Print window now assigns the report name as the document title, replacing what was previously a blank title, so the printed document is easier to identify from the print dialog or saved PDF.
Aggregation is now supported for dataset fields in raw data Excel export, so exported raw data can include summary values instead of only the unaggregated rows.
The Report Viewer gained six new locales, Estonian, Greek, Indonesian, Thai, Latvian, and Lithuanian, extending the viewer’s language coverage for teams working in those regions.
The new FillEmptySpace custom property fills empty space after table items using table rows, so layouts with variable-length tables no longer leave an awkward gap at the bottom of the page.
Reverse proxy support now routes the application based on the request domain, eliminating the need to use the application URL across the entire Bold Reports operation.
Kubernetes deployments can now use the Traefik load balancer as a modern, supported alternative to NGINX Ingress.
Dataset query filters now accept UUID data type fields in PostgreSQL. Identity and foreign-key columns stored as UUIDs can be filtered directly in the dataset, without casting them to text in the query first. This removes a common workaround where authors had to wrap a UUID column in a cast expression just to build a working filter, so filter conditions on ID-based fields are now as straightforward to set up as on any other column type.
Introducing the new on ReportModified event, which triggers whenever any RDL object is updated, letting host applications track changes, trigger custom workflows, and build smarter integrations for improved development efficiency and control.
Serialization of Username and Password nodes in the RDL is now restricted during on-premises download, keeping data source credentials out of downloaded definitions.
Additional application security improvements were made for a smoother and safer experience.
Schedules can now use expression selection alongside parameter selection when they are created, so a schedule’s parameter value can be tied to a dynamic expression instead of always being fixed at creation time.
The report server architecture was upgraded to .NET 10, keeping the server aligned with Microsoft’s current long-term support runtime for better performance and security.
Bold Reports now supports the Hebrew locale in the Report Server interface, extending the platform’s language coverage with a right-to-left locale.
Added support for skipping emails from the report server when a scheduled report contains no data, so recipients no longer receive empty or near-empty report emails on runs that had nothing to report.
Error messages for the export report API were made clearer, making failures easier to diagnose from the API response alone.
A health check option was added to Report Server for deployment and uptime monitoring, so orchestration tools and load balancers can probe server health directly.
Provided support to validate report parameters for the add and update schedule APIs, so parameter values passed to these APIs are checked against the report’s actual parameters.
Scheduling intervals can now be set dynamically in the report server, instead of relying only on fixed preset intervals.
Fixed startup and default error logs in the report server so they capture accurate information, and added upgrade-case specific error logs, making it easier to diagnose why a failed upgrade didn’t complete.
Embedded iframe scenarios are now supported using JWT authentication, giving host applications a standards-based token option instead of relying solely on the platform’s own auth scheme.
The profile, help link, and notification options in the header can now be hidden using custom_ui_reports json nodes, letting embedders present a leaner, more branded chrome.
The add user API now supports setting a username directly instead of deriving it from other fields. This gives integrators explicit control over the username value when provisioning accounts programmatically.
The export file name for a scheduled report can now be set through the add and update schedule APIs, instead of always falling back to a default generated name.
A new Report Viewer Preview custom property, EnableFitContentMaxHeight, resolves textbox overlapping that could occur when cell content is rendered at its natural size.
The Pyramid chart preview now allows flexible label rendering adjustments, giving report authors more control over how category labels display around the pyramid shape.
HTML export and printed reports now support custom fonts, so documents render with the precise font styling defined in the report instead of falling back to a default typeface.
DataTable generation for the WebAPI data connector is faster, reducing the wait when a report backed by a Web API source is previewed or refreshed.
Report processing cancellation events are now supported in the Writer component, letting host applications abort a long-running export instead of waiting for it to finish or time out.
Bold Data Hub moved from Python 3.11 to 3.13, bringing newer language features and performance improvements to pipeline execution.
Automated deployment of Azure App Services is now supported, along with improvements to automated rebranding in Bold Reports deployments, reducing the manual setup needed for cloud rollouts.
The user management service (ums) architecture was upgraded to .NET 10, keeping identity and user management aligned with the platform’s current runtime.
The logging mechanism now uses a standardized PascalCase variable naming convention across services, making logs easier to read and correlate when diagnosing an issue that spans multiple services.
