Error
Malformed records detected in error parsing
Your dataset contains invalid formatting
Cause
There is a formatting issue with the data set being imported into the table.
Solution
Imported datasets are placed in a "staging" status when errors are detected. To resolve this error, you'll need to remove the dataset from the table and review your source data.
Some common issues to look for in your source data:
- Commas that have been replaced with a different symbol
- Entries in a row that contain a comma without surrounding double quotes
- Entries with a quotation mark that are not escaped (surrounding double quotes)
- An uneven number of columns and rows
We also recommend reviewing the source data best practices below. Once you've scrubbed your data, select Import from the menu to add the dataset back into your table.
Source data best practices
To help ensure data integrity and extensibility, follow these best practices for the source data you upload to tables:
- Save static and unique identifiers—such as account numbers or IDs—to identify each record in your data. While names and other identifiers may be easier to recognize, they can also change over time.
- Ensure the first row of your dataset—after the header—is representative of your data. When you upload a dataset, Wdata automatically suggests the columns' data types based on the values in the first row.
- Don't save formatting such as currency symbols. Wdata automatically removes these when it uploads the data to a table.
Note: When you upload decimal values, you can select the format of the imported numbers.
- To enable collaborators to slice-and-dice data effectively, upload the lowest level of data.
Note: Don't use _filename, _tags, _timestamp, or _userID as column IDs. To avoid conflicts, Wdata automatically skips columns with these IDs during import.