Overview
The DatasetFile configuration and properties in the Dataset module allow you to manage and customize configuration to read and write recipes or configuration from text files.
On this page:
Configuring DatasetFiles
To create and configure a DatabaseFile follow these steps:
- Access Datasets → Files.
- Click the plus icon.
Enter a Name and Description for the new File.
Click Ok.
The new DatasetFile object will show up in the DataGRid. To edit any property of the new DatasetFile, double-click the property you wish to edit on the corresponding row. The table below describes each available property you can configure for your DatasetFiles.
Column | Description |
|---|---|
Name | The DatasetFile object''s name. The system will warn you in case of you choose an invalid name. |
FileName | Specify the full path to the File. The file path can have Tag values embedded using curly bracket syntax. For example ExampleFile{{tag.Test}}.txt. When executing, the area in curly brackets is replaced by the Tag's value. |
FileType | Specify the file type. The following options are available:
|
Objects | Click the button with three dots (...) to select the tags that you want to populate with data from the file with data from specific columns. |
Description | The description for the File. Provide a meaningful description to make it easier to execute maintenance in the future. |
XMLSchemaType | Represents the schema type of an XML file, which can be:
|
Enabling DatasetFiles on the Solution Explorer
You do not need to worry if you do not find the menu Dataset Files option under Dataset. The DatasetFile option may not appear due to a filter option in the platform, which shows only the mostly commonly used features.
To change, follow the steps below:
- Access the Home Page by clicking on the house icon.
- On the Home Page, under the Solution Explorer Preferences, select Show All Modules and Features in the Filter option.
Alternatively, you can change the Filter option by using the Filter selector on the sidebar, as shown in the image below:
In this section...