The built-in Reporting feature allows you to configure how your dashboards are synced. Reporting Services are a hosted solution that requires Application Workspace to have internet access.
The Standard license (included in Application Workspace) will only allow the Reporting feature to work based on the last two months of data.
Built-in Reporting vs Reporting via the Power BI template
The built-in Reporting feature is currently in preview. Since it is a hosted solution, certain data of applications used by customers is collected as described in Section C of the Data Protection Information and in accordance with our privacy statement.
As an alternative to the built-in Reporting functionality, we recommend using the Power BI Template Reporting feature (described below), which is generally available.
The following options are available:
Status of the Reporting Service:
- Unconfigured - is not enabled for the local zone
- Disabled - is disabled for the local zone. Contact the support department for more information
- Configured - is configured for the local zone but has not been synchronized yet. It can take up to 24 hours for the first synchronization to occur.
- Warning - Data has been synchronized but not completely. See the Result field for more information.
- Failed - An error occurred while synchronising with the local zone. See the Result field for more information.
- Synchronized - Data has been synchronized with the local zone
Result - This can be a warning or an error message which describes what error occurred during the previous synchronisation.
External URL - The URL which should be used by the cloud solution to access the Application Workspace Server. Typically, it is your FQDN.
Synchronized at - The last time the data from Application Workspace was synchronized with the dashboards. Data is synchronized within an interval of 24 hours.
Test connectivity - Clicking this button initiates a remote connection request to the local zone to verify that everything is set up correctly. The button becomes available once the zone is configured for reporting.
NOTE: It can take up to 24 hours before new data becomes available.
Firewall prerequisites
If you have a firewall in place that filters the communication between the local Application Workspace System and the Application Workspace Reporting Services, you must configure the following settings in order for the Reporting feature to work properly.
Inbound rules
| DNS | Port |
|---|---|
| report-service.liquit.com | 443 |
| report-service-outgoing.liquit.com | 443 |
Outbound rules
| DNS | Port |
|---|---|
| report-service.liquit.com | 443 |
As an alternative to the built-in Reporting functionality, you can use our Power BI template, which is hosted externally and is not yet integrated into the Application Workspace. The Power BI template allows you to retrieve data directly from the software database, without relying on a data window.
Although it currently provides access primarily to events data, the template significantly expands reporting capabilities by offering greater granularity and a wider range of insights — including licensing, deployments, launch health, install health, and more.
You can download the Power BI template from the Integrations section of the Application Workspace Downloads site. Availability starts in Application Workspace version 4.4.
Licensing
The Power BI template is supported for all three license types: Standard, Access Manager and Release and Patch Management.
Create a username and password for the Power BI Template
To configure the OData Feed Connection for the Power BI template, you must first create a username and password in Application Workspace.
1. Navigate to Manage > System > API Access.
2. Click 
Create in the table toolbar.
3. In the Create client secret window that open, add a description and select an expiration date. By default, the field is prefilled with a date two years from today. If left blank, the expiration will be set to 'Never'.
4. In the Summary window, click Finish to generate the client secret.
A confirmation dialog, Your client secret has been created, will appear. This contains the password for the Power BI OData Feed Connection.
5. Open the newly created client secret to view the username.
NOTE: The username is a static value that is unique per zone.
For more information, see API Access.
Upload the Template to Power BI Tools
You can upload the .PBIT template to any of the Power BI tools that supports publishing templates to an on-premises Power BI Report Server, such as Power BI Desktop (Optimized for Power BI Report Server), Power BI Service, and Power BI Report Server.
We recommend Microsoft Power BI Desktop 2.147.1088.0 64-bit (September 2025) (Optimized for Power BI Report Server).
Configure the OData Feed Connection
To configure the OData feed connection:
1. Open the Power BI tool, followed by the template, and insert the Zone URL. The format of this URL is https://<virtualhost>/api/reports/v4/.
2. On the Basic screen, enter the username and password you generated in Application Workspace, as described in Generating the username and password in Application Workspace for the Power BI Template.
NOTE: We recommend keeping the prefilled level of authentication as-is. Changing this setting has no impact on the connection or data access.
