Telerik blogs
ReportingT Report ServerT_870x220

Telerik Reporting enables developers to quickly report on data from their applications. Follow along to go through an example using Telerik Reporting with Kinvey's BaaS.

Using Telerik Reporting with Kinvey's BaaS provides an efficient data to reporting workflow. Let’s imagine, after using Progress Kinvey to quickly build and deploy your application, people are using it, they love it and then comes the need for some reporting about the application and its users. This is where Telerik Reporting shines.

In this post, we are going to use the sample application from Kinvey Studio to build a couple of reports using Kinvey’s BaaS. The Kinvey Studio sample is a vehicle fleet manager application. As the Senior Report Designer, our task is to create one report for Vehicle Inspections and another for Ticket Requests. Although before we start, there are a few house cleaning items.


  1. Kinvey Account
    • Create a free account at
    • NOTE: Use the same credentials as the Telerik Account
  2. Kinvey Studio Installed
  3. Telerik Account
    • Create a free account at
    • NOTE: Use the same credentials as the Kinvey Account
  4. Telerik Reporting Installed

Getting Started with Kinvey's BaaS

After we have all the prerequisites set-up, we need some data and a backend before we can start building our reports. Kinvey Studio has a nice sample that takes just two clicks. To do this, open Kinvey Studio and create a Sample App. The following is a visual walk-through.

1. Start by opening Kinvey Studio from the Windows Start Menu
Open Kinvey Studio

2. Log in and Create an App
Create Sample Kinvey App

3. Name it, store and describe it

Progress Fleet Manager Sample Details

Voilà! That’s it. We have a RESTful API backend, some data, and a couple of users to work with.

Understanding the Data

An important aspect of using Telerik Reporting with Kinvey’s BaaS is understanding the data. Because of this, it deserves its own section. The key items are Collections, Querying the API and the Data Model. Let’s review them next.


The backend is a MongoDB (NO-SQL) database that contains collections of Entities. For the “non-mongo” aficionados, collections are sets of JSON documents and Entities are the basic unit of data in the form of key-value pairs.


Since Kinvey’s REST API is the interface to the MongoDB database this enables Mongo’s powerful query language. The general format of the RESTful API is as follows:[APP_KEY]/[COLLECTION_NAME]/?query=[FILTERS]&[MODIFIERS]

Additionally, using the Kinvey API Console we can test our queries.

Kinvey API Console For more details on how querying works in Kinvey, see the Querying the Kinvey Data Source documentation.

Data Model

The model we are working with here is simple. There are collections of Inspections, Tickets, and Vehicles. Below is a screenshot of the Kinvey Console and another for the table representation.

The Kinvey Collections View

Kinvey Collections Console

The Table Representation

Table View Data Model

Bringing it All Together

Let’s look at what some actual queries against our Kinvey Back-end would look like.

A query used to get all the vehicles would be:[APP_KEY]/vehicles/

A query used to get a single entity would look like below:[APP_KEY]/vehicles?query={"[KEY]":"[VALUE]"}

The following is the query for getting a single vehicle:[APP_KEY]/vehicles?query={"vehicleId":"[VEHCILE_ID]"}

All right, we have a basic understanding of what our backend is, what it looks like and how to get data. Let's build some reports.

Building Reports in Telerik Reporting

We’ll focus on two simple reports. The first is a Vehicle Inspections Report and the second is a Ticket Requests Report. I’ll go over each in more detail as we build them. But first, let’s review connecting the API.

Connecting the Data

We’ll use the Web Service Data Source in Telerik Reporting. The data source uses two types of authentication, Basic and 2-Step (Bearer). For simplicity, we are using the Basic configuration. This is a username and password combination which has been provided for us in the sample. Let’s review setting this up.

1. Open the Stand-Alone Designer
2. Select the Data Tab
3. Choose the WebServiceDataSource
4. Configure the Data Source as Follows

NOTE: This demo backend will be deleted by the time this goes live.

1. Enter the URL Query String Enter the URL Query String

2. Enter the Username and Password
NOTE: The demo username and password combination is UN: admin and PWD: admin
Configure Basic Authentication

3. Preview the data
Preview the Data

That's all we need to configure the Web Service Data Source. Let's build some reports.

Creating the Vehicle Inspections Report

With this report, we are going to display the inspections that have been completed for each vehicle. This will require a filter on the data at the table level. Additionally, we’ll need a dropdown to select the Vehicle number and view the inspections.

  1. Create the Vehicles Data Source
    • URL:[APP_KEY]/vehicles
  2. Create the Inspections Data Source
    • URL:[APP_KEY]/inspections
  3. Create the Vehicle Id Report Parameter
    • Use the Vehicles Data Source
    • Properties:
      • Display Member: = “VIN: “ +
      • Value Member: = Fields._id
      • AutoRefresh: true
      • Visible: true
      • Value: = First(Fields._id)
  4. Create Table to display Inspections
    • Use the Inspections Data Source
    • Filter the Table based on the report parameter
      • Filters: = Fields.vehicleId = = Parameters.vehicleId.Value
    • Sort the data in ascending order
      • Sortings: = Asc
    • Set the No Data Message
      • NoDataMessage: = “No Inspections”
    • Drag desired fields to respective columns
Here is an animated view of Using the Vehicle Inspections Report.

Vehicle Inspections Report Animated

Creating the Maintenance Ticket Requests Report

With this report, we are going to display Ticket Details by type of Ticket. The filter will apply at the data source level and will filter by a property value and not a unique identifier. In most cases, this would provide a list of duplicate items. However, a nice feature is Reporting automatically configured the query to select distinctly. This is nice for non-indexed properties.

  1. Create the Type Data Source
    • URL:[APP_KEY]/tickets
    • Create Query Parameters with the below name and values
      • Parameter 1: Name=query; Value={}
      • Parameter 2: Name=fields; Value=type
  2. Create the Tickets data source
    • URL:[APP_KEY]/tickets
  3. Create the Report Parameter
    • Use the Type Data Source
    • Properties:
      • Display member: = Fields.type
      • Value member: = Fields.type
      • AutoRefresh: true
      • Visible: true
      • Value: =First(Fields.type)
  4. Create Table to display tickets
    • Use tickets data source
    • Filter Table data based on the report parameter
      • Filters: = Fields.type = = Parameters.Types.Value
    • Drag desired fields to respective columns
Here is an animated view of using the Ticket Maintenance Report.

Using the Ticket Maintenance Report

What's Next

As seen in this post, Telerik Reporting is a powerful tool for designing reports from many different data source types. But reports are not useful unless they communicate information. This leads to another important feature of reporting; the delivery. Telerik Reporting can deliver reports in many different form factors with a Build Once, Deliver Everywhere approach. Let’s look at how this might work.

Reporting can host reports in various applications using Report Viewers. These include mobile-friendly Web, Windows Forms and WPF applications. With the use of Report Viewers, reports can be easily shared in different formats like PDF, XLSX, and Word. Additionally, these formats can be delivered via export or email. The best part is that all this functionality is available to the user directly from the Report Viewer with minimal code and configuration.

For Enterprise scenarios, our Report Server allows for collaborative delivery. Viewing reports is the same through a Report Viewer except designers work on a report that is a single source of truth and the report is delivered as it is updated. Additionally, the Report Server includes a RESTful API that can be used to build custom application integrations.


In closing, integrating Telerik Reporting with Kinvey’s BaaS enables an efficient data to report workflow. Nowadays, web data is moving rapidly and with the use of NO-SQL databases, the shape of the data is ever-changing as well. Telerik Reporting and the Web Service Data Source provides seamless integration with a RESTful API that can be used to build and deliver reports at a speed compatible with web data.

About the Author

Eric Rohler

Eric was a Technical Support Engineer at Progress.

Related Posts


Comments are disabled in preview mode.