This is an old revision of the document!
Table of Contents
EXPORT DATASET (.dset)
Category: Export / File
Description
This action exports a dataset (tabular data) into a file in the native EasyMorph format (.dset). The native format allows very fast loading of the data into EasyMorph as there is no data conversion.
One .dset file contains one dataset.
Use cases
When working with large datasets that require significant load times, converting the source tables to .dset files and loading those into the workflow can increase overall process performance.
Action settings
| Setting | Description |
|---|---|
| Export to | Select whether the .dset file will be written to a local file (on your system) or to an EasyMorph Server. Options: Local file or EasyMorph Server. |
Local file settings
| Setting | Description |
|---|---|
| File* | The fully-qualified file name of the output dataset (includes relative or absolute path). |
| File already exists | If a file with the same name already exists, choose whether to overwrite the existing file, rename the existing file, or halt the action's execution. See the "File already exists options" table below for details. |
| Encrypt columns | When checked, one or more columns in the dataset will be encrypted and require a password to access. See the "Encrypt columns options" below for details. |
* Setting can be specified using a parameter.
EasyMorph Server file settings
| Setting | Description |
|---|---|
| Link to Server | Select to use the pre-configured link to an EasyMorph Server. (Use the Start screen to configure the Server Link if you haven't already done so. |
| Connector* | Select the pre-configured connector to the EasyMorph Server. |
| Path* | The fully-qualified file name of the dataset. |
| File already exists | If a file with the same name already exists, choose whether to overwrite the existing file, rename the existing file, or halt the action's execution. See the "File already exists options" table below for details. |
| Encrypt columns | When checked, one or more columns in the dataset will be encrypted and require a password to access. See the "Encrypt columns options" below for details. |
* Setting can be specified using a parameter.
File already exists options
| Option | Description |
|---|---|
| Overwrite | The new file replaces the original file. |
| Rename | The original file will be renamed with "backup" and a serial number appended to the file name. The new file will possess the name specified in the File or Path setting. |
| Halt project execution | The project will stop processing and this action will display a warning symbol. |
Encrypt columns options
| Option | Description |
|---|---|
| Password | Provide the password that will be required to access the encrypted data. |
| Encrypt columns | Select whether to encrypt all columns in the .dset file, or just selected columns (and choose which columns to encrypt). |
Remarks
When importing a dataset (.dset) file with encrypted columns, the Import dataset action icon will initially appear with a warning symbol and no data will show in the data grid. Enter the Password in the action settings to decrypt and view all columns.
If you do not have access to a dataset's password, select Load only selected columns and scroll down the dataset's column list. Encrypted columns will appear with "lock" next to their names. Select only unencrypted columns and click "Apply" to display those columns' data in the data grid.