InMemoryDataProviderWrapper: Data Provider on Steroids

The features of different data providers vary widely. Depending on the data source, sorting, native aggregate functions or filters at database level may be available directly. Or not. For example, none of this is available in file-based formats such as JSON or XML, or even in “web” formats such as REST. These are typically read “front to back” and therefore cannot offer sorting or native aggregation. With List & Label 29, we have something new to offer.

Enhanced Drag & Drop Support in the Designer

A frequently asked question was: “Why can’t I see the relations in the report designer?” This question refers to the variable/field window, in which 1:1 relationships were displayed, but not (the usually much more important) 1:n relationships. In short, our answer was always: “The relations are there, but only in the object window, e.g. when creating tables”. We even put the long answer in a Knowledgebase article.

Powerful, Reusable Subreports for Your Reports

Often reports consist of similar, repetitive sections like a number of charts or crosstabs just filtered for different categories but otherwise identical. Or tables and subtables that have a preselected set of columns you want to have wherever this table is used. List & Label 26 now helps you and your users to get rid of the tedious task to maintain such reports and apply changes to all instances of objects. You can add real subreports that contain exactly the required items and maintain those in one single place.

Keeping Groups of Table Lines Together

Continuing our quest to make the table object more versatile and powerful in LL25, we added an important tweak to the way table lines are kept together. Before, you just had the choice between keeping all lines together or none. That means, if the output for a single record stretched over a couple of pages and consisted of several line definitions, there was hardly ever a way to get the wrapping "right". 

Autosize for Column Widths

Another step forward in our continuing quest to improve what's already great – our table object. Until LL25, you had to decide which widths you'd like to reserve for your respective columns. While this works out just nice most of the time, sometimes the result is less than perfect.