.NET

Top-N and “Others” for Crosstabs

by
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

by
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.

Cross-Row and Column References for Crosstabs

by
cross-row and column References for crosstabs

From the latest blog post you could already tell that the crosstab is one of our focus areas for version 22. Besides multiple result cells we decided to pay a visit to the crosstab functions as well. In version 21 these functions can already be used to reference the values of sum cells, column and row labels etc. By extending the functions slightly, striking new features become available.

Enabling Multiple Result Cells for Crosstabs

by
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.

Progress OpenEdge Reporting Tool List & Label 21

by
This time we feature a guest post from our partner and developer colleague Thomas Wurl. About two years ago, Thomas developed a free data provider for Progress OpenEdge available for all List & Label customers. While this provider was adopted successfully by many Progress users, it suffered some restrictions. So Thomas decided to restart from scratch and came up with an incredibly fast and powerful new solution. Here's his story. 

What Our ALM Toolchain Looks Like

by
I'd like to take the time after the release of LL21 to give you a short tour of what our ALM tool chain looks like. You probably have the same needs and challenges in your everyday jobs that we have. It was a process of trial and error until we arrived at our current configuration. While we are happy with it for the time being, it's always good to keep an eye on new stuff – so this is the current state of development as of 01/2016 :-).

Introducing C++ Support for Multiple Report Containers

by
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.

The Challenging Road to Release

by
We're quickly approaching the final release of List & Label 21. As you surely know from your own practice, release times are hard times ;-). You are moving constantly between madness and excitement. To visualize the long and challenging road we're about to finish, we created the following infographic.

Scripting Support in Functions

by
List & Label has a very powerful formula language. Most manipulations one could think of are possible out of the box or can be realized by using a user defined designer function. However, the latter requires you as a developer to think of the need before deploying your application. In LL21, we'll introduce a new feature that allows to use C# or scripting host languages like VBScript directly in the function wizard.

Essentials

New Version 30
Web Report Designer
Report Server
Report Server Apps
License FAQ
Buy Now
Blog

For Customers

My combit
TeamViewer

Partners

Resellers
Technology Partners
Partner Area

Company

About us
News
Press Center
Contact
Awards & Accolades

List & Label Newsletter

Don’t miss out on new features, service packs, how-tos and exclusive sales offers.

Subscribe

© 1989-2025 combit GmbH | All rights reserved | Legal Notice | Privacy Notes

Follow usfacebookLinkedIn YouTube GitHub Reddit