New GraphQL Data Provider for List & Label
GraphQL was publicly released in 2015 and became quite popular since then. It's used by a number of big web applications like Instagram, Facebook and others.
GraphQL was publicly released in 2015 and became quite popular since then. It's used by a number of big web applications like Instagram, Facebook and others.
While for standard tasks the default mechanism for Rscript rendering of List & Label might be sufficient and convenient to automatically generate the png, jpeg or svg chart output from a Rscript on the fly, there might be situations where you simply desire more control.
List & Label has supported a number of text based export formats for quite a while. You can have XML, CSV and layout TXT export in different variants. That way, you can use List & Label as a convenient way to convert your data from one of the supported data sources to something you can use in other applications again. But one very popular format was missing so far that's been around for quite a while: Java Script Object Notation aka JSON.
This is another of those "huh, you didn't have that before" features. As a WYSIWYG layout oriented reporting tool, the page has always been king for List & Label. While this is nice in many circumstances, when it comes to reporting for the web or XLS and printing is not planned at all, the result can be unwanted although looking beautiful.
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.
It’s been a while since the original announcement back in June 2016, but hey, we’re finally there. Today marks the release of a brand new VCL component that uses the data provider interface and FireDAC at its core.
Continuing our quest for an improvement of the Designer’s refactoring features, it’s obvious that finding text alone is only halfway to quickly and easily refactoring your projects to accomodate them to changed field names, table names or other identifier changes. So we decided to take this project one step further and offer a powerful replace feature in LL24.
With the help of Javonet, the List & Label .NET component can be easily integrated and used directly from Java – with the usual ease of use you are accustomed to from .NET. With this cooperation, Java customers have easy access e.g. to real data preview in the Designer, drilldown reporting and report parameters to name just a few of the interactive features.
List & Label's powerful filter options could not be used for all data sources so far. Reason is, especially for web based data sources, it is not possible or feasible to get "all" data first and then filter to the desired subset. The upcoming version 24 comes with a powerful new feature that addresses this very issue: Parametrized Data Sources. It allows to combine data source parameters with actual report parameters in the Designer.
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.