What’s New in Bold Reports v3.1.31 Release

Connect to MariaDB and MemSQL (SingleStore) data sources in reports

MariaDB 

Enterprise Reporting

Now, you can create data sets from these data sources.

Embedded Reporting 

Common features 

Offline installation setup

We now have offline installation support for the Bold Reports Embedded Reporting build. Use the unlock key file to proceed with the offline installation. If you do not have the unlock key file, you can get it from our website.

Report Viewer

Reports execution logs

We have provided support to log execution information about the reports that are viewed and exported using Report Viewer in the IReportController interface.

The execution logs are used to analyze the users’ actions in terms of reports viewed, exported formats, the amount of time spend on specific reports, etc.

Sample Code :

public class ReportViewerController : ApiController, IReportController,
BoldReports.Processing.IExecutionLogger
{
public void UpdateExecutionLog(BoldReports.Processing.ExecutionInfo executionLogInfo)
{
//Add your changes
}
}

Document map support for viewing and export

We have provided document map support for the web and desktop Report Viewers. A document map contains navigational links to the reports that are made in the Report Viewer.

Screenshot :

Keep report header row visible while scrolling

Prevent row and column labels from scrolling out of view after rendering a report. You can now freeze the row or column headings.

Screenshot :

Improved dependent parameter loading indicator

When a dependent parameter’s parent parameter is changed, use a parameter-specific loading indicator.

Screenshot :

New PowerPoint and HTML support in ASP.NET Core app

Export rendered reports to PPT and HTML documents in ASP.NET Core apps.

Report Writer

• Export PDF and Excel documents with document maps for easy page navigation.
• Utilize improved date-cell value formats applied in Excel documents.
• Export reports as PowerPoints in UWP Report Viewer.

Report Designer

Set intervals for category and value axes in the chart report item

In the chart report item, we have provided a property to set the interval for category and value axes. The interval property allows you to define the number of intervals you want in the category (x) and value (y) axes and it provides the consistent measurement of the data points in the chart report. Usually, the value axis will be the y-axis.

Example:

To check the sales of shop owners.

Set the interval type as Numbers and the interval value will be 15,000.

Now, you can see the difference of the value (x) axis range from 15,000.

Set custom attributes for series in the chart report item

Now, we can set the custom attribute property for all chart categories. Format the chart using a few simple moves, and change the default border style, palette, and drawing style. These features produce the largest visible change on the chart.

Example:

Adjust the point-width value to 0.1 and set the drawing style to bar.

Now, see the output.

Adjust the point width value to 0.6 and the drawing style to the cylinder.

See the output now.

Lookup and LookupSet expressions in the Expression dialog box

Lookup : 

We can use the Lookup expression to retrieve a value from a specified data set for a name-value pair where there is a 1-to-1 relationship.

The general structure of the Lookup expression is as follows:

Lookup(source_expression, destination_expression, result_expression, dataset)

Example :

The user wants the name of the product by comparing the product ID with the ID from the product table. You can refer to the detailed example also here.

=Lookup(Fields!ProductID.Value, Fields!ID.Value, Fields!Name.Value, "Product")

LookupSet: 

The LookupSet function is used for a 1-to-many relationship between two data sets.

The general structure of the LookupSet is as follows:

LookupSet(source_expression, destination_expression, result_expression, dataset)

Example:

The user wants the name of a store if the territory group ID and the ID match.

=LookupSet(Fields!TerritoryGroupID.Value, Fields!ID.Value, Fields!StoreName.Value, "Stores") //returns an array of values

Report Viewer improvements

General improvements in Report Viewer

You will see these below improvements in our Embedded Reporting and Report Viewer SDK.

• Report printing works well in Blazor applications.
• The default parameter values are processed properly in en-GB culture.
• The Report Viewer print option is displayed on all devices and the text content displays without any overlapping.
• If the report path has been empty, the control properly resets, and it shows an empty view

Tablix improvements 

• Tablix columns are rendered properly based on a dynamic visibility expression.
• Table bottom borders are displayed properly in view and export.
• The toggle and sorting actions are working properly inside tables.
• Since there is no data in the table, it is rendered as an empty table.

Chart improvements

• The intervals of a doughnut, column, and radar charts have been improved.
• The chart axis labels are properly rendered in the date-time format.
• The rendering of chart axis labels in the thousand-separator format has been enhanced.
• Stacked column charts render with proper series values and legend.

Page setup improvements

• When refreshing a report, no additional pages are inserted, as well as the values in the Page configuration dialogue are sufficiently updated.
• The page setup dialog is properly displayed relative to the control in all browsers.
• The report content margins are properly applied in printed documents.

Report Designer improvements

You will see these below improvements in Embedded Reporting and the standalone designer.

• Resolved the maintaining format property values in table cells.
• The nullable property-value reset action in report parameters while editing a data set has been fixed.
• Resolved format and expression value resetting issue when changing the font styles in table cells.
• Fixed the filters and parameter collection reset action when editing a shared data sets.
• Resolved the exception thrown while passing parameter values as headers in the WebAPI data source.

Conclusion 

We are happy to share these updates for Bold Reports v3.1.31 with you, and we hope you find them useful. Check them out and let us know what you think on Twitter, Facebook, LinkedIn, or Instagram. If you have any questions, leave a comment below. To keep saving time with your reporting solutions, stay tuned to Bold Reports.