Share this page

# OData support for extended reporting

This section describes how to work with OData for extended reporting capabilities.

In this topic:

## Overview

OData (Open Data Protocol), the OASIS REST-based standard for consuming REST APIs is supported. You can use business intelligence (BI) tools that support OData to connect to your project data and generate charts and reports. This enables you to visualize and analyze the data using extended reporting capabilities, beyond the functionality provided by reports and graphs.

Here is the workflow of working with OData.

1. Prepare for the OData connection, as specified in Prerequisites.

2. Retrieve project data over OData using BI tools that support OData (such as Power BI and Tableau).

   For details, see Connect to project data from a BI tool.

3. Process retrieved data before analysis.

4. Use the BI tool to generate reports and charts for the project data.

Back to top

## Supported OData versions

OData version 4.0 is supported.

Any tool that supports OData version 4.0 is likely to work. For a list of tools that support OData, go to OData Ecosystem and select Consumers.

The OData support has been tested with Power BI and Excel.

Back to top

## Supported entity types

After connecting to your project from a BI tool, you can retrieve the following project data:

- Releases

- Cycles

- Requirements

- Test folders

- Tests

- Test design steps

- Test set folders

- Test sets

- Test instances

- Test runs

- Users

- Defects

Back to top

## Prerequisites

Before working with OData, gather the following connection information:

Prerequisite | Details
--- | ---
Enable OData support | To enable the OData support, set the IS_ODATA_SERVICE_ENABLED parameter to Y. For details, see Site Parameters.
OData data source URL | Project data can be accessed through a unique OData data source (or OData feed), allowing users to seamlessly connect to the data through different BI tools. The OData data sources follow the URL format of: https://<server>/qcbin/odatasvc/domains/<domain_name>/ projects/<project_name>. For example, you use the following data source URL connect to connect to the DEFAULT/Demo project data. http://<server>/qcbin/odatasvc/domains/DEFAULT/projects/Demo To include data from multiple projects, enter the data source URLs for these projects one by one.
Sign-in credentials | You use API keys to connect to an OData data source. Complete the following for your user account: Generate an API key for your account. Note down the client ID and API key secret. Enable OData for the API key. For details, see API key management.
Enable full name support | Required only if you want to retrieve users' full names. By default, only usernames are retrieved for users. If you also want to obtain the full names, set the IS_ODATA_SHOW_FULL_NAME site parameter to Y. Note: Consider your organization's policy before you enable the full name support.
Install private certificate | If a private certificate is used in your environment, make sure the certificate is also installed on the machine where your BI tool is running.

Back to top

## Authenticate

Authentication is required the first time you connect to an OData data source from your BI tool.

Use the basic authentication option in your BI tool.

You authenticate with the client ID and API key secret associated with your account.

Field | Description
--- | ---
User name | Enter the Client ID.
Password | Enter the API key secret.
Select which level to apply these settings to | Varies on BI tools. Specify the level where the username and password can be shared for authentication: http://<server>/qcbin/odatasvc/domains/. You can use the username and password to connect to any projects of any domains in the specified server. http://<server>/qcbin/odatasvc/domains/<domain_name>.You can use the username and password to connect to any projects under the specified domain.

If your client ID or API key secret is no longer valid, the authentication fails. Edit or clear permissions to authenticate with your new credentials.

Back to top

## Connect to project data from a BI tool

You can use any business intelligence tool that supports OData to connect to your project data, such as Power BI, Tableau, and Excel.

Example: Connect to project data from Power BI

1. Open Power BI. Select Home > Get Data > OData feed.

2. In the OData feed dialog box, select Basic, enter your OData data source URL, and click OK.

3. Select Basic, and enter your sign-in credentials.

Example: Connect to project data from Tableau

1. Open Tableau. From the side menu > Connect > To a Server, select More and then OData.

2. In the Server field, enter your OData data source URL.

3. In the Authentication field, select Username and Password.

4. Enter your sign-in credentials.

Example: Connect to project data using Excel

1. Open an Excel worksheet. Select Data > Get Data > From Other Sources > From OData Feed.

2. In the OData feed dialog box, select Basic, enter your OData data source URL, and click OK.

3. Select Basic, and enter your sign-in credentials.

Back to top

## Process retrieved data before analysis

This section lists some recommendations about processing project data before you work on them using your BI tool.

- Filter data

- Expand data

- Build entity relationships

Filter data

If you want to work on narrowed-down data, you can filter retrieved data by table columns of the following types:

- ID. For example Defect ID.

- Time. For example Actual Fix Time.

- Date. For example Closing Date.

When using filters, only the And operator is supported.

Expand data

When connecting to an OData data source with multiple tables, you can use the expand option on a table column to add additional columns from the related table. This helps you build queries across tables. The expand option is recommended for one-to-one entity relationships only.

For example, the Defects table contains references to several related tables, with the Releases table among them. You can use the expand option on the target_rel column of the Defects table to add more columns related to releases, for example, the name column. After the target_rel column is expanded, one more column named with target_rel.name is added in the Defects table.

Here is another example about expanding the detected_by_user column of the Defects table. Select full_name, and then the detected_by_user.full_name column is added.

Note: Whether you can add users' full names depends on whether the support for retrieving full names is enabled. For details, see Enable full name support.

Build entity relationships

Create relationships between tables to accurately calculate results and display the correct information in your analysis. This is especially necessary when you are dealing with one-to-many, many-to-many, or multiple-level entity relationships.

Below is a relationship for test set folders, test sets, test instances, and tests.

Back to top

## Troubleshooting

The following table list the issues you may encounter when using OData.

Issue | Solution
--- | ---
`OData: Request failed: The underlying connection was closed: Trust could not be established for the protected SSL/TLS channel` | This may happen because you use a private certificate on yourenvironment but do not install the same certificate on the machine where your BI tool is running.

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: