Common Errors FAQ
The authoritative, detailed error-troubleshooting table lives on Data Package Validator — check there first. This page adds two things that table doesn't cover:
- A mapping from error message → underlying rule type, so you can predict which other templates might hit the same error class.
- A few error messages sourced directly from the validation engine's message properties this session, which weren't already represented in the troubleshooting table.
Error → rule type cross-reference
| Error you see | Underlying rule type | Also see |
|---|---|---|
| "The character count exceeds the database column width" | Column length check (not a named rule type — enforced directly against Text, max N characters) |
How to Read the Template Documentation |
| "User defined ID is already in database" / "...already in package" | check-value-in-entity / user-defined-ID uniqueness tracking |
Validation Rule Glossary |
| "Missing conditional required value" | Conditional-required field check (driven by a template's ConditionalRequired + Conditions) |
ReadingTemplateDocumentation.md |
| "Value reported in template does not match preferred vocabulary" | Controlled-vocabulary check against an lk_* table |
Template Catalog → Lookup Tables |
(new) "{0} for {2} is already defined for a {1} in {2}" |
check-value-not-in-entity |
Seen in study_design_edit's arm_2_subject section — see Subject Sharing Across Studies for exactly when this does (and doesn't) fire. |
| (new) A row's computed required/reference status doesn't match what the template demands (e.g. "subject ID must always be for a new subject") | values-equal |
Validation Rule Glossary |
Additional source
ImmPortValidation_troubleShooting_errors.xls (in the DataSubmissionProcess documents folder) is a spreadsheet version of common validator errors — useful as a secondary reference if the page above doesn't cover your specific message.
If you hit an error not described anywhere
Contact the ImmPort Helpdesk (mailto:ImmPort_Helpdesk@immport.org) with the exact error text, the template name, and the row/line number — don't guess at a fix based on a similar-looking error for a different field, since conditional-required triggers are template-specific.