Deploy Report Server on an Azure Container Instance and using it from an Azure Function

Report Server Azure Container

As we keep getting requests to support calling List & Label from an Azure Function, and – due to several restrictions like e.g. GDI sandboxing – List & Label can’t be used directly in this context, I thought it might be interesting to explore another way to the cloud, this time using the Report Server. Using its REST-API, you can even create reports from an Azure Function. But let’s walk through the process step by step.

New Service Pack 27.002 for List & Label and the Report Server

The new service pack for List & Label 27 brings many enhancements and improvements especially for the new Web Report Designer as well as for Delphi and .NET developers. In addition, the new drag & drop interface for charts now also supports the selection of an aggregate function. The report template preview in the Report Server uses the new Web Report Viewer, styled according to the applied Report Server customization. Read our blog post for more highlights. The individual entries have been taken directly from the English readme.

Report Server 27: New Features and Improvements

In the Report Server’s most current version, a few more exciting new features have been implemented, as a response to some customer requests. Overall, the new Report Server now visually integrates better into your application. Also, in addition to new actions for planned reports, it also offers additional enhancements for Excel export. Service Pack 27.001 will provide customers with a completely new preview.

Porting to .NET Core: Report Server on New Technology Basis

The Report Server saw the light of day in 2014. At that time, version 1.0 was implemented using the ASP.NET MVC framework and was based on List & Label 19. But as the number of users increased in subsequent versions, so did the requirements and ideas for new features. Some of the customer requests were difficult to realize with the underlying technology. Many developers have certainly been faced with the same question: What should we do next?

 

New Connection to Microsoft Flow for the Report Server

Microsoft Flow allows you to define your own processes and workflows based on various triggers. More than 200 services such as Office 365, Facebook, WordPress etc. are available for this purpose, which can interact with each other in the workflows (called flows). These services offer actions as well as triggers, such as when a file is created (on Google Drive, DropBox or also on alternative services like e.g. box) or when a mail is received. Each flow has a trigger and may have multiple actions. This article describes how to connect combit Report Server to Microsoft Flow.

New Apps for the combit Report Server

This post belongs to a series of blog posts that are dedicated to the innovations of combit Report Server 24. At this point I would like to recommend the two posts "What's New in Report Server 24, Part 1" and "What's New in Report Server 24, Part 2".

Today we are talking about the new native iOS and Android apps for the combit Report Server, which allow you to access the reports on your Report Server directly from your smartphone or tablet. Previously, this was also possible directly via the Report Server web interface, but the new apps offer additional options and a device adapted and fast operation, as you would expect from a native app.

Reporting REST with parameters, authenticating via tokens with the Report Server 24

This is the first of two blog posts presenting the new features of our combit Report Server in the upcoming version 24. Since the last version, in which the Report Server has become part of our List & Label developer component, the development teams of both products have been working even more closely together. This enables us to better coordinate the needs of both products, and thus also of our customers.