PDF is by far the most important export format and one of the targets virtually every user is actually working with. Over the years, we've employed a number of different SDKs and versions of these SDKs in order to write decent PDF files. While the results were excellent already for "normal" cases, there were a couple of restrictions in more advanced scenarios. This has changed in version 26.
Thanks to all participants for taking the time to answer our questions. One thing that I can say straight away: your time was well invested. Your feedback has given us many good ideas and suggestions on how we can further improve List & Label and which new features and technologies are important to you. We do not want to withhold the results, so here are your answers from the survey.
As a proud platinum sponsor, we just attended the all-virtual VSLive! VirtCon as an exhibitor. For me, it was actually a revisit, although my last VSLive! experience dates back some time ago. I've been to San Francisco in 2002 when .NET 1.0 was first launched by Bill Gates himself. At least the travel wasn't that exhausting this time :).
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.