Progress® Telerik® Reporting R3 2019

Report Designer Tools

Use Report Designers to create Telerik Reporting report definitions. We provide two report designer options. Both report authoring environments include features such as WYSIWYG report design surface, enhanced support for expressions and wizards for creating graphs, maps, crosstabs, tables, band, and label reports. Define interactive features such as parameters, bookmarks, drillthrough and drilldown actions.

Standalone Report Designer

Standalone Report Designer is a standalone desktop application that features an easy to use environment:

  • Does not require Visual Studio;

  • Works with XML report definitions packaged in a zip archive (.TRDP) or in plain legacy format (.TRDX):

    • No need to recompile your projects when modifying the report definition;

    • No need to upgrade - you can directly open older report definition with a newer version of the Standalone Report Designer, report viewer or report service; The report definition will be automatically upgraded when edited and saved with the Standalone Report Designer;

    • This format can be stored and managed with the Report Server and other kinds of storages such as a database;

    • The recommended XML report definition format is TRDP due to the following reasons:

      • The report resources are stored in the zip so the report definition is faster to handle and more compact.

      • Supports report Localization.

Visual Studio Report Designer

Visual Studio Report Designer is a report authoring tool that runs in Visual Studio:

  • Works with .NET type report definitions (.CS or .VB files):

    • More difficult to maintain - the project should be built every time a report definition is modified and you should go through the Upgrade Wizard when upgrading your Telerik Reporting installation;

    • Support for report events, still Telerik Reporting provides other declarative means to handle most of the complex tasks. For more information see Report Events;

  • Due to Visual Studio assembly caching mechanism, the designer preview is not guaranteed, when using ObjectDataSource Component, EntityDataSource Component or OpenAccessDataSource Component.

In this article
Not finding the help you need?