Reporting — Server-side Filtering of Cascading Parameters, EF Core 6 Support, Stored Procedures with Multiple Data Tables, and More (v22.1)

If stored procedures for your SQL database can return multiple data tables (result sets), we’ve got some good news for you. Our next major release (v22.1), allows you to retrieve all these tables as needed. The following image displays multiple tables from one stored procedure (ProductInfo) within the Field List:

As you would expect, you can display data from each of these data tables within your report. To display data, set your report's Data Member property to the appropriate table (the table that includes the data you wish to display).

Once set, you can drop the table fields from the Field List onto report bands.

Your report document will then display all records from the table:

The same method works for any other data table from for these stored procedures (those with multiple data tables).

We added a new Select data fields page to our MongoDB Data Source Wizard.

This new page allows you to select the data fields that you wish to include in your MongoDB collection (and also change associated display names).

Use the drop-down menu to select the appropriate collection (the collection that includes the data fields you wish to configure).

Enable or disable the checkbox in the Field Name column to include or remove a field from a collection.

Use editors within the Field Display Name column to change default field names.

Note: To generate field types and build its data source schema, the Data Source Wizard analyzes the first 100 documents (if the number of available documents is less than this default limit, the wizard analyzes all documents).

If the number of documents is greater than the default limit, the wizard page includes an Analyze all records button for your convenience (You can click this button to analyze all available documents instead of 100). Please keep in mind that a full analysis might be a time consuming process.

The Federation Data Source allows you to combine data from multiple data sources and apply operations such as Union, Join, and Transforms to the federated data.

In certain cases, you might want to modify federated data after initial configuration. Use our Manage Queries dialog for this purpose (you can invoke the dialog from the Field List).

With v22.1, you can add, modify, or delete queries when using our Manage Queries dialog.

Let's see some basic examples.

To add a new query, click the Add button in the left menu.

DevExpress Reports allows you to create a report parameter (let's call it primary) and use it to filter values for a second parameter. These parameters are known as cascading parameters.

With our most recent release (v22.1), you can filter the values of a secondary cascading parameter at the database level. In the above screenshot, the selected product category contains 15 items. In real-world applications, such a category might contain hundreds or even thousands of products or items. When this new feature is enabled, only filtered values are loaded into the memory. As you might expect, this helps reduce memory usage/allocation.

The following data source types support this new capability:

If you want to apply a filter to the aforementioned data source types at the application level, simply disable the secondary cascading parameter’s DynamicListLookUpSettings.UseServerSideFiltering property. Note: For other supported data sources, cascading parameter filter operations are always applied at the application level.

We’d love to hear your thoughts on these new features. Have we addressed a specific business need? What additional data source-related feature would you like us to introduce in DevExpress Reports?