After you have created your app, you need to load data into it. You can import data from data connections, such as databases, web files, Microsoft Excel spreadsheets, or delimited text files.
Do the following:
-
In the app overview, click Data load editor.
-
Click on a data connection.
Data connections are displayed in the right-hand side of the data load editor.
Information noteYou can only see data connections that you own, or have been given access rights to read or update. Please contact your Qlik Sense system administrator to acquire access if required. -
Select which data file or database to load.
After selecting a data source, the Select data from dialog is opened.
- Select tables and fields to load.
-
When you have finished selecting fields, click Load data.
The Select data from dialog is closed, and the data is imported. The Data load progress dialog shows the results of the data load.
- When the data load is complete, click Close.
You have now loaded data into the app, and you can start creating sheets and visualizations in the app overview. Click and select App overview.
If you want to verify that your data is loaded, click and select Data model viewer.
Troubleshooting
If you load several files, it is possible that a warning message will be displayed after loading the data. Qlik Sense automatically creates links between fields that have the same name, which, in cases where the two fields contain unrelated data, can lead to unintended links. The two most common warnings are:
|
Synthetic keys |
If two tables contain more than one common field, Qlik Sense creates a synthetic key, a composite of the common fields, to resolve the linking. In many cases, you do not need to do anything about this if the linking is meaningful, but it is a good idea to review the data structure in the data model viewer. See: Synthetic keys |
| Circular references |
If you have loaded more than two tables, any fields common to more than two tables may cause a loop in the data structure. It is recommended that you review the links in the data model viewer, and resolve the issue in the data load editor. |