QlikWorld 2020 Global Conference. Join us to discover how to get the most from your data. Act fast. Register now and save.

Azure Storage Metadata

The Qlik Azure Storage Metadata connector uses the Azure Blob API to access your Azure Storage metadata, like the names of files and subfolders in your Azure Storage account.

Note: The Azure Storage Metadata connector is only available on cloud editions of Qlik Sense.

Ways to access your data

To access your Azure Storage metadata, you need to authenticate the connector with your Azure Storage account credentials. After you create a connection, select Azure Storage Metadata as your data source, enter the blob containter path, and select Authenticate. You are redirected to a Azure Storage login page. Log in with your credentials to retrieve an authentication token, and enter it into the connector.

Creating a connection and selecting data

Loading data from tables

After you authenticate the connector with your account credentials, use the tables to fetch your data. Below are use cases for some of the available tables:

Table Description
ListBlobs Use this to list the files and subfolders of a blob repository located in your Azure Storage account.
GetBlobProperties Use this to list the metadata and properties for a blob repository.

To select and load data from a table, enter the required table parameters and click Preview data. Required parameters are marked with an asterisk (*). The table fields are displayed under the Data preview tab. You can select fields individually by selecting the box beside each field name. Select Insert script after you have made your selection.

Creating a connection and selecting data

Reference - Azure Storage documentation

You can refer to the Microsoft Azure Blob service REST API documentation to learn more about the requirements and restrictions imposed by the API.

Microsoft Azure Blob service REST API

Troubleshooting

You receive an error message that you have reached the API rate limit

Possible cause

You have exceeded the API limits that are imposed by the Azure Blob API.

Proposed action

To reduce the impact of reaching API rate limits, develop your app with the following in mind:

  • Extract only the data you need.
  • Reload one Azure Storage-based application at a time.
  • Ensure that loops in your script that make API calls do not result in infinite loops.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?