Data Import without Preparation

Data import is used to load data from the selected source to a standard cube or time series database. The import wizard enables the user to load data to repository using minimal settings and create all the objects required to access this data (cubes or time series databases, dictionaries, and tables).

Import wizard works correctly if the default database is set for the repository.

NOTE. The current implementation enables the user to import data, presented only in JSON format, from a REST source.

Getting Started

Working with Data Import Wizard

Select type of the source, from which import is executed, and click the Next button.

Different objects are created after import depending on the selected type of data consumer (standard cube or time series database).

After executing import, import settings are saved to ETL task, the following objects are created in the folder specified by the user:

A standard cube with the name of the selected import object.
A folder with the name of the selected import object:

ETL task. Task name matches the name of the selected import object. A data provider and data consumer with the names of the selected import object will be created in the ETL task. The selected import object is used as the data provider. A standard cube created during import process or specified as an existing source is used as a data consumer. All necessary parameters for data provider and data consumer are set up in ETL task, parameter values are obtained from the import wizard.
If import object cannot be found in the repository when executing the ETL task, a dialog box opens where the user should add a new imported object.

If an ETL task is started from the task scheduler, and no import object is found, the task is skipped and a message informing that the import object is not found is displayed in the status line.

NOTE. If a local file is used as an import source, the Document repository object is used as a data source (with auto determined type) for the ETL task. In this case the ETL task has the name and extension of the imported file.

The Document repository object. This object is a copy of the imported file and has the same name and extension.

NOTE. If a local data file is specified as a source, the document is created.

Table. The table stores data loaded from source during ETL task execution. The table is named after the import object.

MDM dictionary named Values. The dictionary contains the elements, which names match the names of real fields of the specified import object.
MDM dictionaries. Dictionaries' names match the names of elements obtained on dividing into dimensions. Values of text fields from the import object are imported as values of the Name attribute of standard cube.

NOTE. If data is imported with errors, a cube is not created. As a result, import settings are not saved, and an ETL task is not created.

After executing import, the following objects are created in the folder specified by the user:

Time series database named after the selected import object.
Folder named after the selected import object that contains MDM dictionaries. Dictionaries' names match the names of the imported data provider fields.

No ETL task is created after executing import to a time series database, unlike the case of data import to a cube.

NOTE. If data is imported with errors, the time series database is not created.

After executing import, data is available for analysis. If any errors occurred during the import, the Data Import Conflicts dialog box opens after the import is finished. Examples of import from table and crosstab are given in the Import Examples section.