Answer: When a component ID contains more than 14 characters, the system sends a generic error message via email stating: "There has been an unexpected error in the system. Some of your records might not have been processed. Please Review."
Other possible reasons could be:
1. CSV Formatting Issues (Most Common Cause)
The file may look fine in Excel but still be invalid for the uploader.
What to verify
- ✅ File is saved as CSV (Comma delimited) — not CSV UTF‑8, XLSX, or TSV
- ✅ No extra commas at the end of rows
- ✅ Every row has the same number of columns
- ✅ No completely blank rows (especially at the bottom)
Quick test
- Open the CSV in Notepad or Text Editor and ensure values are clean and comma‑separated.
2. Invalid or Missing Required Fields
If Component Tracking expects specific required columns, a missing or malformed value can cause the upload to crash instead of returning a validation message.
Common offenders:
- Blank Component ID / Tracking ID
- Invalid date formats (e.g.,
MM/DD/YYYYvsYYYY-MM-DD) - Numeric fields containing text or symbols
- Leading or trailing spaces in key identifiers
✅ Even a single bad row can fail the entire upload.
3. Special Characters or Hidden Encoding
Non-visible characters can break backend parsing.
Watch for:
- Smart quotes (“ ”)
- Curly apostrophes (’)
- Emojis or symbols (®, ™)
- Non‑breaking spaces copied from Word or email
Fix
- Re-type the affected fields
- Use Find & Replace to remove special characters
- Re-save the file using a plain‑text editor
4. File Size or Row Limit Exceeded
Many Component Tracking uploads have:
- Maximum row limits
- Size limits (even if undocumented)
Try
- Uploading a smaller subset of rows (10–20)
- If that works, gradually increase until it fails
This helps isolate the problematic record.