As of today, there isn't a solution to get an idea of the extension usage. However, I think this is a crucial need, especially when upgrading QlikSense.
So, what I sugget : -a standard usage extension dashboard -the ability to query the data through API.
Best regards,
Simon
Bi Consultant (Dataviz & Dataprep) @ Business & Decision
@Levi_Turner : Thanks. I validated and found that only Extensions of type "Visualization" are extracted. Type "theme" and "mashups" are not pulled. Do you have any plan to include theme and mashups as well?
Theme is a fair ask, but would require a fair bit of work to fetch that metadata. Mashups will always be excluded. At their core, mashups are not inside an app. So the approach of mapping app <> extension does not make sense. It's a fair ask to see whether a mashup has been used but will not be in the scope of the Extension Usage Dashboard.
@Levi_Turner : Sure, If we can extract theme information that will be sufficient for our requirement. please help us once this is possible. Thank you very much.
@Levi_Turner : Extension usage dashboard is failing after QlikSense Upgrade from April 2019 to June 2020 Patch 1. When I run the app it failed while executing below query in "Sheet Owners from QRS" script tab. I noticed that '$(vLibConnect)' used in other script tab also but they executed successfully.
Not sure why it is failing in a particular tab "Sheet Owners from QRS" . I am pasting log file too at the bottom. Can you please help to fix this.
LIB CONNECT TO '$(vLibConnect)';
RestConnectorMasterTable: SQL SELECT "id" AS "id_u2", //"objectType", "engineObjectId", "__KEY_root", (SELECT "id", "userId", "userDirectory", "name", "__FK_owner" FROM "owner" FK "__FK_owner"), (SELECT "id" AS "id_u1", "__KEY_app", "__FK_app" FROM "app" PK "__KEY_app" FK "__FK_app") FROM JSON (wrap on) "root" PK "__KEY_root" WITH CONNECTION( URL "https://$(vCentralHostname)/qrs/app/object/full?filter=objectType eq 'sheet'", QUERY "xrfkey" "abcdefg123456789", HTTPHEADER "X-Qlik-Xrfkey" "abcdefg123456789" );
The extension usage dashboard shows even extension that has been deleted (but without mentioning it's deleted). In my opinion as previoulsy discussed, the root is the use of the Telemetry Dashboard. Extension usage must show only the current metadata while TS must show an historical data. Maybe using API instead of logs would solve that? I'm pretty sure it would take a couple of hours for a qlik dev to make a new monitor rest connection and plug it to the chart.
The sad part is that I have a project that needs to remove all illegitimate extensions and replace it with native object.