Skip to main content

Importing extensions


Importing extensions

By default, only the RootAdmin user has the access rights to import extensions. You need to define security rules to enable others to import extensions. By default, all Qlik Sense users have access to all extensions that you add. Revise the security rule named Extension if you want to limit the access.

Warning: Do not import extensions with the same name as a native object, it is not supported.

Do the following:

  1. Open the QMC: https://<QPS server name>/qmc

  2. Select Extensions on the QMC start page or from the StartArrow down drop-down menu to display the overview.

  3. Click Create new Import in the action bar.

  4. The Import extension file dialog opens. Select a zip file to import.

    Remember to enter the password for the zip file if it is password protected.
  5. Click Open in the file explorer window.

  6. Click Import.

Note: Extensions are saved to \\QlikShare\StaticContent\Extensions. The maximum file size is specified under Limitations in the following topic: Attaching data files and adding the data to the app. If the import of an extension fails, check the log files at %ProgramData%Qlik/Sense/Log/Repository/System.

Extension names

If the name of an extension already exists (or occurs more than once in the zip file), the zip file is not uploaded.

By default, an extension that is imported is displayed in the Extensions overview. The name of the extension will be the same as the name of the .qext file. However, in the Qlik Sense hub, the extension is displayed with its regular file name that can also be changed by editing the Name field in the .qext file.

If you want to only display the file name in the Extensions overview, you must remove the com-qliktech- part from the .js file and the .qext file in the extension zip file.

Note: A user can only change the name of an imported extension in the Dev Hub.
Note: Avoid importing widget libraries from the QMC, because when you do, no check is performed for duplicate library IDs and widget IDs. Import from the Dev Hub instead, where the check is performed automatically .