Adding a Custom Function to the Designer

You can extend the report engine with your own functions that users call from expressions in the web designer.

Adding a Font to the Resource

Fonts can be embedded into a report as resources so the document renders and exports identically regardless of the fonts installed on the server.

Changing the Viewer Theme

The web viewer ships with a set of visual themes and appearance options. This example changes the viewer's theme and background color.

Configuring Report caching

Caching keeps a rendered report on the server between requests, so paging and exporting do not re-render it every time.

Connecting to Data from Code

A report's data can be supplied from the page model instead of the template.

Creating a Custom Button on the Viewer Toolbar

The web viewer toolbar can be extended with your own buttons using its client-side JavaScript API.

Creating a Custom Parameter Panel for the Viewer

Instead of the built-in parameter panel, you can build your own HTML form and feed its values to the viewer through the client API.

Editing a Report Template in the Designer

Embed the report designer in ASP.NET Core Razor Pages, load a template, and connect its editing and save actions.

Exporting and Printing a Report from Code

A report can be printed or exported straight to the HTTP response without the viewer.

Localizing the Viewer

The web viewer interface can be shown in any language by pointing it to a localization file, chosen in the viewer options.

Managing Report Printing and Exporting

When printing and exporting go through the viewer, you can intercept them in the page model to adjust the document or its export settings.

Rendering and Exporting a Report in the Console App

Report generation does not require a web host — the engine runs anywhere .NET runs, including a console application.

Saving a Report Template in the Designer

Embed the report designer in ASP.NET Core Razor Pages, load a template, and connect its editing and save actions.

Sending a Report by Email

The web viewer can e-mail a rendered report from its toolbar. This example enables the button and handles the request in the page model.

Showing a Report in the Viewer

Set up the report viewer in ASP.NET Core Razor Pages, load a template, and connect the component to the application.

Showing Interactive Reports

Interactive report features — sorting, drill-down, collapsing groups, chart interaction — work in the web viewer without extra code.

Using a Custom Data Adapter

For a data source that is not built in, you can register a custom data adapter and use it in the web designer.

Using Business Objects in the Report

Web reports can be bound to your application's business objects — collections implementing IEnumerable or ITypedList.

Using Report Variables in Code

Load the report template in ASP.NET Core Razor Pages, assign its variables from application code, and continue with rendering.

Using the Full-Screen Mode in the Viewer

The web viewer can occupy the whole browser window in full-screen mode, useful for report portals and dashboards.

By using this website, you agree to the use of cookies for analytics and personalized content. Cookies store useful information on your computer to help us improve efficiency and usability. For more information, please read the privacy policy and cookie policy.