Introducing Parametrized Data Sources

example for a result in the html 5 viewer

List & Label's powerful filter options could not be used for all data sources so far. Reason is, especially for web based data sources, it is not possible or feasible to get "all" data first and then filter to the desired subset. The upcoming version 24 comes with a powerful new feature that addresses this very issue: Parametrized Data Sources. It allows to combine data source parameters with actual report parameters in the Designer.

Our Most Popular Resources for Developers

developer team combit

Let's be honest, developing has it's challenges. To meet the ever more diverse demands on applications and technologies, we all rely on a multitude of ressources to make our lives easier. So we, the makers of your favorite reporting tool, thought it's about time to let you benefit from our experience. Below you will find just a small selection of the tools that we can't do without.

Unbelievable Printing Performance Boost

example printing performance boost

Continuing the journey of improving the performance, we decided to tweak a bit on the printing side as well. These optimizations help when using the same table several times with different fields. Think of a tabular report with some charts and a crosstab. Typically you have different views on your data in these objects. For these cases, the improvement is huge – I mean really huge.

Huge Designer Speed-Up for Large Databases

Historically, List & Label has always been working without a database in the background. During the years, we've added powerful databinding to the components, however at the core, the principle stayed the same: your application (or the databinding layer) passes all available data before opening the Designer.

REST API for combit Report Server

order overview screenshot
In our very first blogpost we announced to share updates about the ongoing development of all our products. Until now we put an emphasis on the development of our reporting tool List & Label. But now the time has come to open that focus and give insights on other product news right out of our dev department. That’s why we proudly present our first blogpost on our BI solution combit Report Server:

Introducing C++ Support for Multiple Report Containers

During our Roadshow this fall, the question I was asked the most was “why do you support certain features only for .NET”. Most notably, multiple report containers (since LL20) and nested tables (since LL21) were only available for .NET databinding. The reason for this is the necessity to support a special and – until now – undocumented COM interface for passing the data to List & Label. We decided to leave this interface undocumented in version 20 in order to be free to apply changes without breaking customer code. We had to make sure the interface was ripe. Now we are and here we go.