Data Import Errors & Warnings
See the information below for help troubleshooting errors and warnings that occur when importing data into Data Workbench via FTP.
Errors
You must resolve all errors before Data Workbench can import your data. See the Actions column in the table below for details about how to resolve each error.
Error No. | Type | Message | Explanation | Actions |
---|---|---|---|---|
G-001 | Global | Package could not be imported |
Data Workbench was not able to import the package. This error accompanies any Package- and File-type errors. |
|
L-001 | Load | Package could not be loaded |
During the import process, Workbench was unable to load the data due to a system issue. |
|
P-001 | Package | Manifest file could not be read |
The manifest file for your package is missing, is not structured correctly, does not have the correct File.Name, or is empty. |
|
P-002 | Package | Study |
The |
|
P-003 | Package | Source value not provided |
The manifest file didn’t provide a |
|
P-004 | Package | User does not have access to study |
You don’t have access to the Study you’re attempting to import data into. |
|
P-005 | Package | Study not specified |
Your manifest file is either missing the |
|
F-001 | File | File could not be found: |
Workbench couldn’t find the file in your ZIP package. |
|
F-002 | File | Additional file |
Your ZIP package contains a file (CSV or otherwise) that is not described in your manifest file. |
|
F-003 | File | Required column mapping for |
One or more of your files doesn’t have an object for a required column mapping in your manifest file, or that object isn’t correctly formatted. |
|
F-004 | File | File |
Workbench could not match the column mapping in your manifest file to the columns in the CSV. |
|
F-005 | File | File |
Your CSV file has at least two (2) columns with the same name. For example, the Form uses the same Item twice in a single Item Group. |
|
F-006 | File | Form file name |
Your CSV file’s name is invalid. |
|
F-007 | File | File with no name will be ignored |
A file in your package doesn’t have a file name. |
|
D-001 | Data |
|
The value provided for Study doesn’t match the Name of the Study from the manifest file. |
|
D-002 | Data |
|
The value provided for |
|
D-003 | Data |
|
The value provided for |
|
D-004 | Data |
|
The Event Definition specified exists, but the Event hasn’t been added to the subject’s Casebook. |
|
D-005 | Data | Value |
Workbench couldn’t read the column value provided. |
|
D-006 | Data |
|
The row in your CSV file has more cells than there are columns. |
|
D-007 | Data | Item configs on form |
One or more keys for an item’s |
|
D-008 | Data | Item config |
The Item is missing the |
|
D-009 | Data | Item config |
Your item’s configuration can only include strings and objects, not an array. |
|
D-013 | Data | Item config |
The |
|
D-016 | Data | Missing value for mapped column |
The |
|
D-024 | Data | Multiple subjects exist in Site |
There is more than one Subject at the chosen Site that matches the Subject provided in the CSV file. |
|
D-025 | Data | Duplicate, unequal item config |
An Item exists on more than one Form, but the item’s definition parameters are different for each Form. |
|
D-027 | Data |
|
The value you provided for this configuration is invalid. |
|
D-028 | Data |
|
The value you provided for this configuration can’t have more than 1 value. |
|
Warnings
While Data Workbench does not require you to resolve every warning before importing your data, Workbench may ignore certain Items and exclude them from import. Warnings that cause data to be ignored are marked with an asterisk (*). See the Actions column in the table below for details about how to resolve each error.
Warning No. | Type | Message | Explanation | Actions |
---|---|---|---|---|
F-008 | File | Config [sequence] will be deprecated in [20R1]. Updated manifest file touse [formsequence] |
Your manifest file uses the sequence configuration, which was deprecated in the 20R1 (April 2020) release. |
|
D-010* | Data | Field |
While you can include as many fields as you’d like for item configuration in addition to those required, Data Workbench ignores these fields. |
|
D-011* | Data | Value |
The field’s value is intended to be numeric, but Workbench can’t interpret it as a number. |
|
D-012 | Data | Value |
The value provided in the CSV doesn’t match the configured format pattern for the Item (for Items with the Date, Time, and DateTime data types). |
|
D-014 | Data | Item config |
The Date, Time, or DateTime format you provided in the Item configuration is not supported by Data Workbench. |
|
D-015 | Data | Duplicate data row ignored |
The CSV file contains duplicate rows, based on the keys defined in the manifest file to uniquely identify a row. By default, uniqueness is defined by Study, Site, Subject, and Event. |
|
D-017* | Data | Value |
The value provided in the CSV is longer than the maximum allowable length specified in the Item configuration (for Items with the Text data type). |
|
D-018* | Data | Value |
The value provided in the CSV is less than the minimum allowed value specified in the Item configuration (for Items with the Integer and Float data types). |
|
D-019* | Data | Value |
The value provided in the CSV is greater than the maximum allowed value specified in the Item configuration (for Items with the Integer and Float data types). |
|
D-020* | Data | Value |
Data Workbench can’t interpret the value provided in the CSV file as the data type configured for the Item. Data Workbench ignored this value during import. |
|
D-021 | Data | Value |
Data Workbench can’t interpret the value provided in the CSV file as the data type configured for the Item. Instead, Data Workbench imported the configured default value. |
|
D-022* | Data | Item config |
Your float-type Item confiugration has a Precision that is greater than the Length. Data Workbench ignores both and uses the default. |
|
D-023* | Data | Item config |
Your number- or integer-type item configuration has a Minimum Value ( |
|
* This warning results in data or configuration being ignored during import.