When a dataset is initially loaded into the Transformer page, one or more steps may be automatically added to the new recipe in order to assist in parsing the data. The added steps are based on the type of data that is being loaded and the ability of the application to recognize the structure of the data.
When a text file is used as an imported dataset,
|D s product|
NOTE: Assessing the file encoding type based on parsing an input file is not an accurate method. Instead,
NOTE: In some cases, imported files are not properly parsed due to issues with encryption types or encryption keys in the source datastore. For more information, please contact your datastore administrator.
As needed, you can change the encoding to use when parsing individual files. In the Import Data page, click Edit Settings in the right-hand panel. For more information, see Import Data Page.
Automatic Structure Detection
Tip: If you select the delimiter in a column with a very large number of delimiters, any suggestion card limits the split to a maximum of 250 columns. You can edit the suggested transformation to increase the number of split columns as needed. Increasing the limit can impact browser performance.
When a dataset is imported, the application may infer the names of your columns from the first row of the dataset.
Tip: Avoid importing data that contains missing or empty values in the first row. These gaps can cause problems in your headers.
- In some cases, the application may be unable to create this header row. Instead, the columns are titled
column3and so on.
- If the column names are split across multiple rows in your dataset, you may need to modify the header transformation step. For more information, see Rename Columns.
Microsoft Excel files are internally converted to CSV files and then loaded into the Transformer page. CSV files are treated using the general parsing steps. See previous section.
- For JSON files, it is important to import them in unstructured format.
requires that JSON files be submitted with one valid JSON object per line.
D s product r true
- Multi-line JSON import is not supported.
- Consistently malformed JSON objects or objects that overlap linebreaks might cause import to fail.
Some characters in imported datasets, such as
NUL(ASCII character 0) characters, may cause problems with recognizing line breaks. If initial parsing is having trouble with line breaks, you may need to fix the issue in the source data prior to import, since the Splitrows transformation must be the first step in your recipe.