Years 1900–2050. Dates must match the template's parse format. Required columns must be present. Here's the full validation surface for scheduled imports.
Date range
Date values in all scheduled imports (POs, Actuals, Line Items) must have a year between 1900 and 2050 inclusive. Any date with a year outside that range fails the row and stops the run.
Common out-of-range causes:
-
Typos in the source —
3020instead of2030,1019instead of2019. -
Placeholder dates from upstream systems —
9999,3000,0000often mean "indefinite" or "no end date" in ERPs. Those placeholders fail import.
For the full troubleshooting walkthrough, see Allocadia scheduled import failed: "Invalid date — date outside acceptable range".
Date format
Each date column on the import template has a configured parse format (e.g. yyyy-mm-dd, m/d/yy, dd/mm/yyyy). The data in the file must match that format exactly. Mismatches cause either a parse error or a silent misread (e.g. month and day swapped).
Date-format mismatches are a template configuration issue, not something you can fix in the file alone. Contact Support with the file attached and we'll adjust the template.
Required columns
The import template defines which columns are required. If any required column is missing from the file header, the entire run fails. If a required column exists but a row has a blank value, that specific row fails and the rest of the file processes.
Amount and numeric fields
- Amount columns must be numeric. Currency symbols, thousand separators, or non-numeric characters cause parse failures unless the template is configured to strip them.
- Negative values are typically allowed (used for credits or reversals).
Custom attributes
If your template includes custom attribute columns, the values must be valid for that attribute. For picklist attributes, each value in the file must match an existing option on the attribute (case-sensitive in some configurations).
Comments
Please sign in to leave a comment.