Download Latest Here
The Qlik Sense Extension Usage Dashboard is a Qlik application that parses application meta-data to uncover which applications use extension objects. The sources for this data are the meta-data fetch from the Qlik Sense Telemetry project and QRS API calls. By combining these, we can see which apps use extensions, where those extensions are used, who are the users who use extensions, which extensions are not used, as well as which extension usages could be replaced by a bundled visualization from Qlik.
- Questions answered by the app
- Screenshots
- Requirements
- Installation
- Configuration
- Analysis
- Limitations
- Which applications in my Qlik Sense Enterprise site use extensions?
- For apps that use extensions, on what sheets are they?
- Which extensions are unused?
- Which apps use extensions which can be migrated to bundled visualization objects
- Qlik Sense Telemetry Dashboard installed
- Successful reload of the
TelemetryDashboard-1-Generate-Metadata
task - An operational data connection using Windows authentication to the Qlik Repository Service (QRS)
- Have Qlik Sense Telemetry project installed
- Import
Extension Usage Dashboard.qvf
- Import the qvf into the QMC
- Grant 'Read' access to the
monitor_apps_REST_app
data connection in the QMC (this is a default data connection shipped with the product) to the user that will be reloading the application if it is planned to reload the app from the Hub. Ensure that the user can see this connection in the Data Load Editor. Occasionally this takes a services restart to take effect. - Grant 'Read' access to the
TelemetryMetadata
data connection in the QMC to the user that will be reloading the application if it is planned to reload the app from the Hub. Ensure that the user can see this connection in the Data Load Editor. Occasionally this takes a services restart to take effect. - Ensure that the Qlik Sense service account has
RootAdmin
priveleges. Themonitor_apps_REST_app
data connection is reloaded by the service account, and that account needs access to specific resources via the QRS API that are not available otherwise. - Open up the application and navigate to the Data Load Editor. Navigate to
Config
tab. - Ensure that
vCentralHostname
contains the hostname of the Central Node and is directed to a virtual proxy using Windows authentication. If it has a virtual proxy prefix, be sure to include it (e.g.mycentralnode/myprefix
):
- Reload the application either via a Task in the QMC or as a user other than the service account from the Hub.
The application will provide insight into what Qlik apps use extensions and on what sheet inside of that application the extension resides. The sheets are divided into:
- KPIs: High level KPIs of the use of Extensions across the Qlik site
- Extension Overview: A detail sheet to allow the user to see extension use across sheets. Included is a filter for extensions which are not used in any Qlik app.
- Migration Sheet: A mapping of apps which use extensions which have been added to Qlik’s bundles. These apps can be easily edited to use objects which are now supported by Qlik.
- The Dashboard Bundle, first released in Qlik Sense Enterprise November 2018
- The Visualization Bundle, first released in Qlik Sense Enterprise February 2019
The tool will not record apps which reference extensions which do not exist on the server. Example:
The rationale for this is that in order to determine which visualizations are extensions, (a) we either need to query the installed extensions by name (e.g. barchart-extension
) or (b) inline load a list of visualizations which come with Qlik Sense Enterprise on Windows. (a) will miss usages of visualizations which are not installed, like above. (b) would require that users upgrade this app upon each release of Qlik Sense Enterprise on Windows to ensure coverage for potentially added visualization types (e.g. the Mekko chart
in the November 2019 release). We've made the decision to go with option (a) for a more robust set of coverage across versions of Qlik Sense Enterprise.