Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Apr 16, 2026 10:01:55 AM
Apr 16, 2026 9:59:29 AM
It is possible to save files generated by Qlik Automate (such as reports from the Generate Report and Copy File block) directly to a custom SharePoint document library instead of the default Shared Documents or Documents library.
By default, the Drive ID dropdown in the Copy File block will only show the default library; this article explains how to correctly target any custom library using the List Drives From Site block.
The Microsoft SharePoint connector in Qlik Automate uses the concept of Drives, where each SharePoint document library is a separate Drive with its own unique Drive ID (GUID).
By default, when you use the Copy File on Microsoft SharePoint (or any similar write blocks) and perform a Do Lookup on the Drive Id field, Qlik Automate only displays and allows selection of the site's default document library, which is typically called Documents or Shared Documents.
Even if you have created additional custom document libraries and they appear correctly in the SharePoint Site Contents view as separate Folders, these custom libraries do not appear in the simple Drive ID dropdown of the Copy File block.
As a result, any file copy operation defaults to the default library. If you enter a path such as New Folder/QLIK/filename.pdf, the automation interprets New Folder as a subfolder inside the default library, causing the file to be saved under /Shared documents/New Folder/QLIK/... instead of directly at the root of the custom library.
To target a custom document library, we retrieve its unique Drive ID and then use that ID in the Copy File block. But before we can do this, we need to first discover all available document libraries (drives) on the SharePoint site so we can select the correct Drive ID for the custom library instead of defaulting to Documents.
Do not include the library name in the path.