This was a huge issue, that has been bugging us for years. While – generally speaking – List & Label’s level of printer control is unmatched by any competitor I know of, we always required a printer driver in order to execute this control. On the desktop, that’s all fine and well, as Microsoft conveniently provides the XPS Document Writer and – in more recent versions of Windows OS – the Microsoft PDF Writer. Those are always present and accessible. However, on the web and in the cloud, it’s a different story.
This has been another community suggestion from our Idea Place. Until version 26, you could only have one copy count for labels. This means that the same number of copies were printed for each and every label. In version 26 you can now adjust this individually, based on the data in your data source.
An often required feature for "this cannot be done" type of problems is looking into the future. Things like "don't print this group if it doesn't contain record xy" or "print a reference to the page number of an item that's printed way later". Before List & Label 26, there was no simple solution to this and the magic had to be done in the application if possible at all. Starting with List & Label 26, we'll introduce a new feature that's aimed at solving exactly challenges like this.
Multi-columnar layouts for tables are quite popular for newspaper or phone book style reports. Whenever you have just a few actual columns in the table it's handy to use the page's real estate by splitting it in multiple columns. This feature has been around for ages, however it was missing one important setting until LL25.
No matter which data, using the DataProvider interface you can write your own custom binding. And of course we ship a whole family of providers with List & Label. In LL23, there's a new member of this family that allows your applications to connect to Salesforce data easily.
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.