Troubleshooting Common Outcomes Data Formatting Errors
A practical guide to resolving the most common upload issues, including column mismatches, formatting inconsistencies, and identifier-related errors, to help you finalize your data import smoothly.
Overview
When you upload your outcomes data file, the platform validates it and may return errors or warnings. This article walks through the most common issues and how to resolve them so you can complete your upload successfully.
|
ℹ️ What Changed Errors must be resolved before the upload can be finalized. Warnings are optional fixes that may affect how data displays, but will not block the import. The guidance around student identifiers has also changed in this release. See the updated entry below. |
Most Common Errors
Column Header Mismatch
The column headers in your file must exactly match the template — including capitalization, spacing, and special characters.
-
Example: "Academic Division-School" will fail; it must be "Academic Division/School"
-
Solution: Download a fresh copy of your template from Analyze > Student Outcomes > Upload Data and compare each column header carefully.
Blank Required Fields
Every row must have a value in all required columns. The most commonly missed required field is Outcome Type.
-
Solution: Filter your spreadsheet for blank cells in required columns and either fill in the correct value or remove the row.
Invalid Outcome Type Value
Outcome Type values must match one of the accepted values listed in the formatting guidelines (e.g., Employed Full Time, Continuing Education, Seeking Employment).
-
Solution: Review the NACE First Destination Guidelines or MBA-CSEA Guidelines for the accepted Outcome Type values.
Extra Spaces in Column Headers or Cell Values
Leading or trailing spaces — even a single space — can cause headers to fail validation or create duplicate entries in your data.
-
Solution: Use your spreadsheet application's Trim function (=TRIM()) to remove extra spaces, or do a Find & Replace to clean up headers.
Unrecognized Identifier Columns in File
|
ℹ️ What Changed Previous versions of the outcomes template required you to remove all student identifiers before uploading. That guidance has changed. The updated template now includes two designated, protected columns — User ID and User Email — where you can and should include this information. These fields are never exposed to students or visible in any public-facing area of your platform. If you decide to omit this information, you’ll see a blue info notice appear, encouraging you to consider adding this data.
|
The platform includes backend logic that flags columns appearing to contain student identifiers that do not match the designated template fields. If you receive an error related to identifier columns, it typically means one of the following:
- You have a column containing student IDs or email addresses that is not using the correct template column name (e.g., a column labeled "SIS Number" instead of "User ID").
- You have a freeform notes column that inadvertently contains identifiable information.
- Solution: Review your file for any identifier-style columns outside of the designated User ID and User Email template fields. Rename them to match the template exactly, or remove them if they are not needed. Student names should not be included in any column.
Common Warnings
Annual Salary Values Outside Expected Range
Salary values that appear unusually high or low will generate a warning. This will not block the upload but may indicate a data entry error.
Low Record Count for a Major
If fewer than 5 records exist for a given major, that major's data will not surface in AI Search responses. If fewer than the minimum pool size threshold (default: 10) exist for a given major, that major's data will not display in charts on your Outcomes page (ODV customers only).
Please note: For customers who have purchased ODV, you will have additional options to reduce or increase the minimum number of entries required for visualization. To update those settings, please reach out to our support team.
