Top-N and “Others” for Crosstabs

And while we're at it, let's disclose the last new feature for LL22's crosstab. You were able to design Top-N reports with the crosstab before. The way it works, you choose the required sorting for your group cells, e.g. the category name in the sample of the last post. You're then able to choose the sort order for the items (alphabetically, based on the result value, based on the displayed value).

Automatic Fill-Up for Crosstabs

To continue the quest for the perfect crosstab, welcome to part three of this blog post series. After visiting multiple result cells and cross-column references, today let's look at another cool new feature in the LL22 crosstab – Auto-Fill. This comes in handy whenever there is few data. Think of a yearly statistic where you don't have results for each quarter. Printing something like Q1…Q2…Q4 looks awkward and unprofessional. In LL22 we have the solution to this.

Enabling Multiple Result Cells for Crosstabs

As this was one of the most frequent requested features in our feedback portal and we hadn't visited the crosstab's features for a couple of versions, this feature was an easy pick. A crosstab is aggregating values and groups them by two or even more dimensions. Until version 22, there was exactly one aggregation possible, e.g. you could have either the number of orders or the revenue sum per customer and year, not both. In LL22, there is no limit anymore.

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.

Support for Nested Tables

One of the few requests that kept coming in was "Can we have the detail data in a column of the master table". While there are a couple of workarounds in version 20 that do similar things, the actual request could not be fulfilled this way. Plus, the workarounds were not as discoverable as we would have loved them to be as they included negative indents for line definitions and educated guesses on the number of detail records that are likely to be printed.This is going to change in version 21 – List & Label is going to support a new field type "table" which enables you to nest tables.