This section describes how to use the data load editor to create or edit a data load script that can be used to load your data model into the app.
The data load script connects an app to a data source and loads data from the data source into the app. When you have loaded the data it is available to the app for analysis. When you want to create, edit and run a data load script you use the data load editor.
A script can be typed manually, or generated automatically. Complex script statements must, at least partially, be entered manually.
| A |
Toolbar with the most frequently used commands for the data load editor: navigation menu, global menu, Save, (debug) and Load data. The toolbar also displays the save and data load status of the app. |
Data load editor toolbars |
| B | Under Data connections you can save shortcuts to the data sources (databases or remote files) you commonly use. This is also where you initiate selection of which data to load. | |
| C | You can write and edit the script code in the text editor. Each script line is numbered and the script is color coded by syntax components. The text editor toolbar contains commands for Search and replace, Help mode, Undo, and Redo. The initial script already contains some pre-defined regional variable settings, for example SET ThousandSep=, that you generally do not need to edit. | |
| D | Divide your script into sections to make it easier to read and maintain. The sections are executed from top to bottom. | Organizing the script code |
| E | Output displays all messages that are generated during script execution. |
Quick start
If you want to load a file or tables from a database, you need to complete the following steps in Data connections:
- Create new connection linking to the data source ( if the data connection does not already exist).
-
Select data from the connection.
When you have completed the select dialog with Insert script, you can select Load data to load the data model into your app.
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 – let us know how we can improve!