Skip to main content Skip to complementary content
Qlik Resources
Announcements
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Exporting items

About this task

You can export multiple items from the repository onto a directory or an archive file. Hence you have the possibility to export metadata information such as DB connection or Documentation along with your Jobs, your Business Model, or your Routes and Services, for example. To do so:

Procedure

  1. In the Repository tree view, select the items you want to export.
  2. To select several items at a time, press the Ctrl key and select the relevant items.
    Information noteWarning: If you want to export a database table metadata entry, make sure you select the whole DB connection, and not only the relevant table as this will prevent the export process to complete correctly.
  3. Right-click while maintaining the Ctrl key down and select Export items on the pop-up menu:

    You can select additional items on the tree for exportation if required.

  4. Click Browse to browse to where you want to store the exported items. Alternatively, define the archive file where to compress the files for all selected items.
    Information noteNote: If you have several versions of the same item, they will all be exported.
  5. Select the Export Dependencies check box if you want to set and export dependencies along with the items you are exporting.

    By default, all of the user routines are selected. For further information about routines, see What are routines.

    If you have installed the R2021-06 Studio monthly update or a later one provided by Talend, the Export Dependencies check box is selected by default.

  6. Click Finish to close the dialog box and export the items.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here